NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
what is orbi's tcp session timeout value?
does anybody know orbi's tcp session timeout value? my guesstimate puts it somewhere around 5 or 10 minutes.
ive changed the pace modem back to default of 86400 seconds and the orbi to match. lets see how it does...im a sucker for pain...how do i get it to read out that value to confirm it is there? nevermind...sysctl -a
net.netfilter.nf_conntrack_tcp_timeout_established may not be the right variable to adjust. pace modem continued to climb until internet service interruption. orbi sessions stayed under or around 1000. ive returned orbi to default values. pace modem now set to tcp session timeout = 3600. one of the variables on the orbi must be equivalent to the name used on the pace modem. i spent the last three hours searching openwrt, not sure i found document covering those variables.
Shotround wrote:
net.netfilter.nf_conntrack_tcp_timeout_established may not be the right variable to adjust. pace modem continued to climb until internet service interruption. orbi sessions stayed under or around 1000. ive returned orbi to default values. pace modem now set to tcp session timeout = 3600. one of the variables on the orbi must be equivalent to the name used on the pace modem. i spent the last three hours searching openwrt, not sure i found document covering those variables.
It is really the parameter to change the tcp session timer, but it seems that to take effect it has to be changed in the file /etc/sysctl.conf.
I tried a reboot after changing the value using sysctl -w but the value returned to it's default after the reboot. :(
I also tried the following command (find and replace in the file):
root@RBR50:/# sed 's/7440/7430/' /etc/sysctl.conf (since 7440 is the only such value in the file :) )
The value was taken momentarily but changed back immediately to it's original value. Looks like the file sysctl.conf is -somehow- protected from being changed,
I will keep trying to see if there is a way :)
chmod? i havent touched linux in 20 years. i only went deep enough to satisfy curiosity on an old 486. maybe it was a 386. i would rather see this parameter on the UI for the greater good of users. anyways, the affect of increasing it on the orbi to match the pace gateway may not be a great idea.
i suspect internet connected devices are opening a session and leaving it open. then the orbi kills them at timeout (7440 seconds) but the gateway still has it open until timeout (86400 seconds). then the device wakes up after 7441 seconds and opens another session. multiply that by the number of devices. or could it be the orbi not closing sessions at the gateway? at some point the gateway becomes saturated until x number of sessions timeout.
i think this is better presentation of the above. https://wiki.dd-wrt.com/wiki/index.php/Router_Slowdown
edit: nest products reported lost connections twice last night. changing pace gateway to 1800 seconds. orbi still default.
Thanks for sharing the wiki, it's very good.
Shotround wrote:
....... anyways, the affect of increasing it on the orbi to match the pace gateway may not be a great idea.
........
Yes, I agree. but for if you want to test anything then the following command will do:
sed 's/7440/7430/' /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established --green is current value, red is new value
The value will be effective after setting but will not be stored after reboot. I could not find a way to permanently store it, still looking :)
