Results 1 to 2 of 2

Thread: ip_conntrack_generic_timeout: No such file or directory

  1. #1
    Join Date
    Aug 2010
    Beans
    18

    ip_conntrack_generic_timeout: No such file or directory

    Hi,

    I've followed a few guides on the internet to increase the limits for tcp/ip filtering such as those below:

    /etc/sysctl.conf
    net.netfilter.nf_conntrack_max=131072
    net.ipv4.netfilter.ip_conntrack_generic_timeout=12 0
    net.ipv4.netfilter.ip_conntrack_tcp_timeout_establ ished=54000

    These settings no long seem to be applying? Have they changed in newer kernels?

    sysctl: cannot stat /proc/sys/net/ipv4/netfilter/ip_conntrack_generic_timeout: No such file or directory
    sysctl: cannot stat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established: No such file or directory

    Thanks

  2. #2
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,521
    Distro
    Ubuntu Development Release

    Re: ip_conntrack_generic_timeout: No such file or directory

    The issue is that the files are not present until after the conntrack module is loaded, which is typically sometime after the sysctl stuff runs. In my case the conntrack module is loaded when my iptables rule set loads, so I make the changes at the end of my iptables script. See also.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •