Bug #1970
closedIPsec stops routing after a while
100%
Description
Using the same setup as this bug:
http://redmine.pfsense.org/issues/1969
It appears that after a while with no clear trigger, even Shrewsoft VPN client will stop routing traffic after a while. I have noticed that it seems to happen after I have been connected, then left and had my computer hibernate. Upon returning and reconnecting, the VPN will not route any traffic at all until I restart the pfsense box, at which point it starts working again.
It may be the same issue as the other bug above, but I cannot reliably trigger it by simply connecting and disconnecting (whereas with the Cisco client, the first connection breaks things).
EDIT: It looks like a connection interruption triggers this-- I can make it happen by disconnecting and reconnecting the wireless without properly disconnecting from the VPN.
As in the other bug, let me know if access to this test box would be useful-- I have no concerns about giving access to the interface, as it is simply a test box.
Configuration details:
pfSense 2.0 (release), i386
on a Dell Dimension 420
Using Mobile IPsec--
Providing a virtual IP and DNS
Phase 1 settings:
Interface: WAN
Auth Method: Mutual PSK + Xauth
Negotiation: Agressive
My identifier: My IP address
Peer identifier: UDN (user@domain.com)
preshared key: mypks
Policy Generation: on
Proposal checking: obey
Encryption: AES128, with MD5
DH key group 2
Nat Traversal enabled
DPD on, 5 seconds, 5 retries
Phase 2:
Mode: tunnel
Local network: 0.0.0.0/0
Protocol: ESP
Encryption: AES, 3des
Hash: md5
PFS off
Files