From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] ipsec: Add script to ensure VPNs are always on
Date: Wed, 05 Feb 2020 12:36:14 -0500 [thread overview]
Message-ID: <8cdb5ccc-5e67-5268-8a89-a46b069a4d8f@rymes.com> (raw)
In-Reply-To: <36D59040-B7E1-4713-816F-40A2EF440D7A@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On 02/05/2020 12:22 PM, Michael Tremer wrote:
> Hi,
>
>> On 5 Feb 2020, at 17:19, Tom Rymes <trymes(a)rymes.com> wrote:
[snip]
>> OK, I see what you mean. May I suggest that we eliminate the distinction between "Always-On" and "On Demand" and just retain the time limit for inactivity? Tunnels set to have a limited time before being shut down to inactivity shouldn't be brought back up by the script and those that do not should be.
>
> That would still change one more thing. We would then decide to always keep all tunnels up. I am not sure if that has any disadvantages for anyone really. But we would definitely have to drop the timeout, too, because otherwise the tunnel will be brought down and the script will bring it back up again shortly after.
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.
Does that make sense?
Tom
next prev parent reply other threads:[~2020-02-05 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:24 Michael Tremer
2020-02-05 11:24 ` [PATCH 2/2] ipsec: Silence charon Michael Tremer
2020-02-05 15:25 ` Tom Rymes
2020-02-05 16:55 ` Michael Tremer
2020-02-05 17:16 ` Tom Rymes
2020-02-05 15:23 ` [PATCH 1/2] ipsec: Add script to ensure VPNs are always on Tom Rymes
2020-02-05 16:53 ` Michael Tremer
2020-02-05 17:19 ` Tom Rymes
2020-02-05 17:22 ` Michael Tremer
2020-02-05 17:36 ` Tom Rymes [this message]
2020-02-06 15:03 ` Michael Tremer
2020-02-06 20:06 ` Tom Rymes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cdb5ccc-5e67-5268-8a89-a46b069a4d8f@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox