It looks like 1.2.3.5 is the IP address of the nexthop router on the way to 6.7.8.9.
So it goes 1.2.3.4 —> 1.2.3.5 —> … —> 6.7.8.9. Does that help explain anything? Is there some configuration value I have that would allow for this? I’ll double check to make sure I didn’t make a mistake anonymizing this. On Aug 27, 2018, at 1:14 PM, Paul Wouters <p...@nohats.ca<mailto:p...@nohats.ca>> wrote: On Mon, 27 Aug 2018, Craig Marker wrote: Subject: Re: [Swan] NATD IP different than configured IP Is this the ipsec status output you’re looking for? This is from the client machine. + ipsec whack --status 000 using kernel interface: netkey 000 interface lo/lo ::1.2.3.4@500 000 interface lo/lo 127.0.0.1@4500 000 interface lo/lo 127.0.0.1@500 000 interface enp3s0/enp3s0 4.3.2.1@4500 000 interface enp3s0/enp3s0 4.3.2.1@500 000 interface enp7s0/enp7s0 1.2.3.4@4500 000 interface enp7s0/enp7s0 1.2.3.4@500 000 interface enp7s0:1/enp7s0:1 2.2.3.4@4500 000 interface enp7s0:1/enp7s0:1 2.2.3.4@500 000 interface enp10s0/enp10s0 10.10.20.254@4500 000 interface enp10s0/enp10s0 10.10.20.254@500 yeah. assuming you didn't make a mistake anonymising this, it could never use 1.2.3.5 as its local IP. So I have no idea what's happening in your case. Paul
_______________________________________________ Swan mailing list Swan@lists.libreswan.org https://lists.libreswan.org/mailman/listinfo/swan
