public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Strongswan and auto=start
Date: Wed, 27 Feb 2019 16:46:55 +0000	[thread overview]
Message-ID: <03715558-2162-4317-B4A9-1DE8E24F161B@ipfire.org> (raw)
In-Reply-To: <32FF8B0B-1D8C-4964-85B4-77DC6598F63D@rymes.com>

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

Hi,

No, auto=start was the default.

I would prefer to have auto=route as the default.

When you say you did that for years you are referring to your own setup, right?

-Michael

> On 25 Feb 2019, at 23:16, Tom Rymes <trymes(a)rymes.com> wrote:
> 
> Would it not be possible to revert to the old CGI, prior to On-Demand and change the auto=start line to auto=route? We did that for years.
> 
> Tom
> 
>> On Feb 18, 2019, at 6:43 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hi,
>> 
>> I tried to change this in the CGI, but it is not so easy.
>> 
>> But I would be in favour of On-Demand being the default.
>> 
>> Best,
>> -Michael
>> 
>>> On 18 Feb 2019, at 04:44, Tom Rymes <trymes(a)rymes.com> wrote:
>>> 
>>> A while back, I made a feature request to allow configuration of the Strongswan “auto” parameter via the WUI. This made its way into the WUI as the “On-Demand” feature a while back (thank you!!!) https://bugzilla.ipfire.org/show_bug.cgi?id=10733
>>> 
>>> At the time, I had posted a few links to messages on the StrongSwan mailing list that indicated that auto=route results in superior reliability, and our experience bears this out, but the default remains “auto=start”.
>>> 
>>> In order to support Windows roadwarrior connections, IPFire’s host cert needs a dns Subject Alt Name, so I had to delete all of our tunnels and certs, then recreate them. This meant that I had to change both sides of ~20 tunnels from the default “Always On” (auto=start) to “On Demand” (auto=route).
>>> 
>>> Coincidentally, this message from one of the developers came across the StrongSwan Users list tonight, which basically makes clear that auto=start should not be used: https://lists.strongswan.org/pipermail/users/2019-February/013373.html
>>> 
>>> The relevant quotation: “Use auto=route. Auto=start is not reliable.”
>>> 
>>> This raises the question as to why auto=start is still the default in IPFire.
>>> 
>>> Thoughts?
>>> 
>>> Tom
>> 
> 


  reply	other threads:[~2019-02-27 16:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EB254A0A-3E29-4A31-984C-20E5853EE9A5@rymes.com>
2019-02-18 11:43 ` Michael Tremer
2019-02-25 23:16   ` Tom Rymes
2019-02-27 16:46     ` Michael Tremer [this message]
2019-02-27 17:12       ` Tom Rymes
2019-03-05 15:28         ` Michael Tremer
2019-03-05 16:51           ` Tom Rymes
2019-03-05 16:52             ` Michael Tremer

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=03715558-2162-4317-B4A9-1DE8E24F161B@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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