[Openswan Users] has interfaces= syntax changed in 2.6.18 ?
OCG Technical Support
support at ocg.ca
Thu Oct 16 14:27:13 EDT 2008
Well, I'm running netkey (Fedora 9 included) in case that is a contributing
factor, but the same line you have chokes on mine...perhaps a bug?
Not sure if this is related, but the pluto debug parameter crypto which
worked fine in an earlier version, causes v2.6.18 to complain with:
Oct 15 18:46:49 firewall ipsec__plutorun: /usr/local/libexec/ipsec/pluto:
unrecognized option '--debug-crypto'
All I did was upgrade openswan and that line in the config caused problems
(so I removed for now).
Thanks,
M
-----Original Message-----
From: Paul Wouters [mailto:paul at xelerance.com]
Sent: October 16, 2008 1:44 PM
To: Michelle Dupuis
Cc: users at openswan.org
Subject: Re: [Openswan Users] has interfaces= syntax changed in 2.6.18 ?
Importance: High
On Wed, 15 Oct 2008, OCG Technical Support wrote:
> Date: Wed, 15 Oct 2008 23:08:17 -0400
> From: OCG Technical Support <support at ocg.ca>
> To: <users at openswan.org>
> Subject: [Openswan Users] has interfaces= syntax changed in 2.6.18 ?
>
> I'm running OpenSwan U2.6.18 and have an odd problem. I have this line in
> my ipsec.conf:
>
> interfaces="ipsec0=eth0"
> On service start I get:
> Oct 15 22:35:19 firewall ipsec_setup: interface `ipsec0=eth0' not
understood
>
> Has this parameter/command changed? All of my googling suggests this
should
> work...
It works for me:
protostack=klips
interfaces="ipsec0=eth0"
[root at bofh openswan-2.6.18]# ipsec --version
Linux Openswan 2.6.18 (klips)
See `ipsec --copyright' for copyright information.
[root at bofh openswan-2.6.18]# ipsec setup start
ipsec_setup: Starting Openswan IPsec 2.6.18...
Paul
More information about the Users
mailing list