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.
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 :)