Thibor 13d Bug: Established State Timeout & Max Connecti

Discussion in 'HyperWRT Firmware' started by Terence, Feb 24, 2006.

  1. Terence

    Terence Network Guru Member

    Router: WRT54GS v1.1
    Firmware: Hyperwrt 2.1b1 + Thibor13d

    I notice something very strange with the Thibor13d firmware.
    Can someone tell me if this is a bug or not??

    I saved these values in Management.asp page.
    Established State Timeout: 1800
    Max Connections: 4096

    Then I ran the following commands, and get the corresponding outputs.

    # cat /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts
    1800 1800 120 60 120 120 10 60 30 120

    # cat /proc/sys/net/ipv4/ip_conntrack_max
    4096

    So far so good.
    Then I rebooted the router, and ran the same commands again:

    # cat /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts
    1800 14400 120 60 120 120 10 60 30 120

    # cat /proc/sys/net/ipv4/ip_conntrack_max
    2048

    After reboot, the timeout and max connections in these files are set to the default instead of using the values set on the Management.asp page. By the way, I don't have a customized Startup Script. So is this a bug?

    And can someone tell me how often are these two files, "ip_conntrack_tcp_timeouts" and "ip_conntrack_max", read by the system? Are they read only once at startup or everytime the router tries to establish a TCP connection or do connection cleanups??
     
  2. Thibor

    Thibor Super Moderator Staff Member Member

    it was a bug and has been fixed
     
  3. Terence

    Terence Network Guru Member

    thx for the quick reply~ ^^
     
  4. Thibor

    Thibor Super Moderator Staff Member Member

    welcome
     
  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