From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPsec: Include ipsec.user.conf at the bottom
Date: Tue, 19 May 2015 16:35:07 +0200 [thread overview]
Message-ID: <1432046107.16602.34.camel@ipfire.org> (raw)
In-Reply-To: <op.xyvz000scahio0@atl-uetersen.atlantisgmbh.local>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Hi,
this is intentional because I use this configuration file only to change
some default settings by adding: conn %default and sometimes using the
setup section. That doesn't work when it is at the bottom.
Depending on what ever you want to do: Isn't it better to integrate that
configuration into the CGI script?
-Michael
On Tue, 2015-05-19 at 16:32 +0200, Larsen wrote:
> Hi,
>
> I noticed that in "/var/ipfire/vpn/ipsec.conf" the line "include
> /etc/ipsec.user.conf" is placed at the top instead of the bottom.
> For us, this leads to the problem that our configuration from
> "ipsec.user.conf" is overwritten by the default configuration from
> "ipsec.conf" when it should be the other way around. Therefore, after a
> restart of the IPsec server (iirc), I have to manually fix this problem by
> moving the line from top to bottom.
>
> Is this by design or is this a bug?
>
> Using IPFire 2.17 (i586) - Core Update 89
>
>
> Lars
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-19 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:32 Larsen
2015-05-19 14:35 ` Michael Tremer [this message]
2015-05-19 14:55 ` Larsen
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=1432046107.16602.34.camel@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