On 02/06/2020 10:03 AM, Michael Tremer wrote:
Hi,
On 5 Feb 2020, at 17:36, Tom Rymes trymes@rymes.com wrote:
[snip]
Sorry for being unclear. There are currently eight options for "Inactivity Timeout", including "Unlimited". I would propose that the script you are adding should only bring back up tunnels whose Inactivity Timeout is set to "Unlimited". A tunnel with a timeout of one hour would time out, go down, and then the script should ignore it.
The inactivity timeout is only active when the connection is in “on demand” mode. The script ignores connections in that mode, so nothing will happen here.
Right, but I had proposed to combine "Always On" and "On Demand" into one, as they will effectively be the same after this proposed change. After this change, unless I am missing something, the only difference will be the "Inactivity Timeout".
If "On Demand" and "Always On" are combined into "Normal" (as opposed to "Wait for connection initiation"), then the script can use the Inactivty timeout to determine which tunnels to bring up. Come to think of it, shouldn't the script also bring up any "On-Demand" tunnels that are set to a timeout of "Unlimited"? I know that we run *all* of our tunnels as "On-Demand/Unlimited" because auto=route is so much more reliable.
It's not really a big deal either way, but if the only difference between "On Demand" and "Always On" after this proposed change is going to be the inactivity timeout, then I'd say merge the two into one and use the Inactivity Timeout of "Unlimited" to denote which tunnels should always be up. It's cleaner and less confusing.
My $0.02.
Tom