public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: Re: IPsec: Include ipsec.user.conf at the bottom
Date: Tue, 19 May 2015 16:55:26 +0200	[thread overview]
Message-ID: <op.xyv02ow5cahio0@atl-uetersen.atlantisgmbh.local> (raw)
In-Reply-To: <1432046107.16602.34.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1214 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.

Which config file exactly do you use?
It sounds like you are using "ipsec.user.conf", but I see "conn %default"  
in "ipsec.conf".

Perhaps we can simply have two includes? One at the top and one at the  
bottom?


> Depending on what ever you want to do: Isn't it better to integrate that
> configuration into the CGI script?

A co-worker has setup IPsec so I am not deeply familiar why he choosed to  
configure it like he did. Afaik, he was following the wiki, but I also  
know that this didn´t went smoothly and he had to correct things with help  
of the forum.
That being said, at the moment IPFire creates the entries in "ipsec.conf"  
and we add the following stuff to "ipsec.user.conf":

conn jdoepc
         leftsubnet=0.0.0.0/0
         leftallowany=yes
         rightsubnet=192.168.110.0/24
         rightsourceip=192.168.110.118
         rekey=no

Is there a better way to do this?
We need "rekey=no" for the connection to be stable with Win7 (more on that  
in a later post).


Lars

      reply	other threads:[~2015-05-19 14:55 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
2015-05-19 14:55   ` Larsen [this message]

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=op.xyv02ow5cahio0@atl-uetersen.atlantisgmbh.local \
    --to=larsen007@web.de \
    --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