[Openswan Users] Openswan: ip xfrm policy shows different data than /etc/ipsec.conf

Paul Wouters paul at xelerance.com
Sun Feb 3 13:00:48 EST 2008


On Sun, 3 Feb 2008, Ian Brown wrote:

> I tried it, unforrunately without success.
>
> I had set tun to 172.16.0.1 on one machine.
> I had set tun to 172.17.0.1 on the second machine.
>
> I get on one machine:
> Feb  3 14:21:24 machine1 ipsec_setup: ...Openswan IPsec started
> Feb  3 14:21:24 machine1 ipsec__plutorun: 104 "linux-to-linux-1" #1:
> STATE_MAIN_I1: initiate
> Feb  3 14:21:24 machine1 ipsec__plutorun: ...could not start conn
> "linux-to-linux-1"
>
> and on the second
> Feb  3 14:19:44 machine2 ipsec__plutorun: 104 "linux-to-linux-1" #1:
> STATE_MAIN_I1: initiate
> Feb  3 14:19:44 machine2 ipsec__plutorun: ...could not start conn
> "linux-to-linux-1"

These are not the complete logs. Please look for more messages in your logfiles.

Paul


More information about the Users mailing list