How to change timeout values in Alchemy 1.0 Final?

Discussion in 'Sveasoft Firmware' started by coffeeborg, Jan 25, 2006.

  1. coffeeborg

    coffeeborg Network Guru Member

    If I use the command "nvram show | grep connt", I get the following results:

    size: 19741 bytes (13027 left)
    rc_firewall=echo 172800 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
    echo 4096 > /proc/sys/net/ipv4/ip_conntrack_max
    echo "600 1800 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts

    As you can see, the ip_conntrack_max value is 512, although my rc_firewall script increases the number to 4096.
    If I use "cat /proc/sys/net/ipv4/ip_conntrack_max", then the result is 4096. Why is there a difference? Are those two different values?

    The next thing I'd like to change is the ip_conntrack_tcp_timeouts=3600 and ip_conntrack_udp_timeouts=3600. How could I change that to a lower value?

    I have WRT54GS v1.0 with Alchemy 1.0 Final

    Thank you.

  2. jchuit

    jchuit Network Guru Member


    In Alchemy the ip_conntrack values are (re)set by use of an internal script and not by use of the NVRAM values

    This script is run shortly before the rc_startup script. This means most setting are already done.

    (Tarifa firmware)
  3. coffeeborg

    coffeeborg Network Guru Member

    Then there is no way to increase ip_conntrack value?
  4. jchuit

    jchuit Network Guru Member

    Put it in the rc_startup, that should work, but most settings are already done.

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice