Your message dated Tue, 21 Oct 2014 23:10:54 +0200
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #714990,
regarding fails to reconnect after IP address change
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
714990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714990
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: strongswan-ikev2
Version: 4.5.2-1.5+deb7u1
Severity: important
charon seems to get stuck with stale IP addresses
e.g. I tether my laptop and get the IP address 192.168.42.40
I start the VPN (ipsec up ...)
I use the VPN for 5 minutes
Un-tether the laptop and connect to a LAN, pick up a new IP address
Now run "ipsec up vpn" again and it is still trying to use 192.168.42.40
as the source IP:
initiating IKE_SA vpn[3] to A.B.C.D
generating IKE_SA_INIT request 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) ]
sending packet: from 192.168.42.40[500] to A.B.C.D[500]
retransmit 1 of request with message ID 0
sending packet: from 192.168.42.40[500] to A.B.C.D[500]
^C
I checked with "ip addr" and I can confirm that the 192.168 address is
not bound to any interface
/etc/init.d/ipsec restart
fixes it and then I can connect using the new IP
While a power user is able to diagnose this issue quickly, it is likely
to be very frustrating for non-technical users who just won't be able to
start their VPN without a reboot
--- End Message ---
--- Begin Message ---
Version: 5.2.1-1
This bug had already been addressed in 5.2.0, and 5.2.1 has lots of
additional fixes related to MOBIKE and network configuration changes
which make roaming absolutely seamless in my testing.
If you're still having issues with the 5.2.1-1 package, please reopen.
Thanks,
--
Romain Francoise <[email protected]>
http://people.debian.org/~rfrancoise/
--- End Message ---
