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.
at 7440 seconds on the isp gateway, tcp sessions doubled to just under 2000 sessions. orbi/debug reports around 600 sessions. i think they should be reporting similar number of sessions. as it times out the orbi, the isp gateway should be timing out shortly after. att uverse pace gateway appears to support 8112 sessions. while the orbi appears to support 65536...ive since changed it 3600 seconds. the number of sessions on the isp gateway continues to drop as time passes, although it is still higher than that reported on the orbi.
i did more googling and it appears one tried and true solution to the double nat is to match tcp session timeout on isp device and router. att uverse dsl gateway by pace allows editing of tcp session timeout, but many do not. netgear please add tcp session timeout field to advanced tab.
other problem is when isp device has ridiculous long tcp session timeout, and the router has short timeout; it can fill up the isp device's nat table (found the proper terminology) or clog up the device. hence the internet service disruption. as stated before, ive reduced tcp session timeout on the isp device and yet to experience internet service disruption.
i should also complain to att for leasing low end equipment supporting only 8112 tcp sessions compared to the 65536 on the orbi. before changing the timeout, it was always around 6000 sessions on the isp device. i guess it didnt take much more to put the hurt on the isp device with everything internet connected in the home.