[Openswan Users] Problem with multiple road-warriors and psk

Andy Van den Heede andy.vandenheede at secuteam.com
Wed Sep 20 12:34:02 EDT 2006


Hello,

 

I have some problems with muliptle road-warriors connections with an
openswan server and two linksys routers (different subnet). I made 2
different ipsec connections in ipsec.conf and also 2 lines in
ipsec.secrets.

I work with different rightid fields and different connection names. The
mode is use is aggressive mode. See below more information. Whe I just
configure 1 connection, there is no problem and is the ipsec connection
working perfect.

 

Openswan version: Linux Openswan U2.4.4/K2.6.16[5.0.3] (netkey)

 

Network:

 

NET 172.16.0.0/24 - FIREWALL WITH OPENSWAN 192.168.192.6 - LINKSYS1
192.168.192.8 - NET LINKSYS1 10.253.253.0/24

 
-- LINKSYS2 192.168.192.241 - NET LINKSYS2 172.16.1.0/24 

 

Ipsec.onf file:

 

conn linksys1

        left="192.168.192.6"

        leftsubnet="172.16.0.254/255.255.255.0"

        leftnexthop=

        right="0.0.0.0"

        rightsubnet="10.253.253.0/255.255.255.0"

        rightid="@linksys1.firewall.local"

        auto="add"

        authby="secret"

        type="tunnel"

        keyexchange="ike"

        auth="esp"

        pfs="no"

        ike="3des-md5-modp1024"

        esp="3des-md5-96"

        aggrmode="yes"

        rekey="yes"

 

conn linksys2

        left="192.168.192.6"

        leftsubnet="172.16.0.254/255.255.255.0"

        leftnexthop=

        right="0.0.0.0"

        rightsubnet="172.16.1.0/255.255.255.0"

        rightid="@linksys2.firewall.local"

        auto="add"

        authby="secret"

        type="tunnel"

        keyexchange="ike"

        auth="esp"

        pfs="no"

        ike="3des-md5-modp1024"

        esp="3des-md5-96"

        aggrmode="yes"

        rekey="yes"

 

Ipsec.secrets:

 

192.168.192.6 @linksys1.firewall.local: PSK "PSK"

192.168.192.6 @linksys2.firewall.local: PSK "PSK"

 

In the /var/log/auth.log i have the following (the openswan tries to
build up the wrong connection!):

 

Sep 20 18:21:09 axsweb pluto[29231]: packet from 192.168.192.8:500:
received Vendor ID payload [Dead Peer Detection]

Sep 20 18:21:09 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #2:
Aggressive mode peer ID is ID_FQDN: '@linksys1.firewall.local '

Sep 20 18:21:09 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #2: no
suitable connection for peer '@linksys1.firewall.local '

Sep 20 18:21:09 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #2:
initial Aggressive Mode packet claiming to be from
@linksys2.firewall.local on 192.168.192.8 but no connection has been
authorized

Sep 20 18:21:09 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #2:
sending notification INVALID_ID_INFORMATION to 192.168.192.8:500

Sep 20 18:21:50 axsweb pluto[29231]: packet from 192.168.192.8:500:
received Vendor ID payload [Dead Peer Detection]

Sep 20 18:21:50 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #3:
Aggressive mode peer ID is ID_FQDN: '@linksys1.firewall.local '

Sep 20 18:21:50 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #3: no
suitable connection for peer '@linksys1.firewall.local '

Sep 20 18:21:50 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #3:
initial Aggressive Mode packet claiming to be from
@linksys2.firewall.local on 192.168.192.8 but no connection has been
authorized

Sep 20 18:21:50 axsweb pluto[29231]: "linksys2"[1] 192.168.192.8 #3:
sending notification INVALID_ID_INFORMATION to 192.168.192.8:500

 

 

Thanks in advice,

 

Andy Van den Heede

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20060920/8a0dcaa0/attachment.html 


More information about the Users mailing list