ipsec auto --up is occasionally started to early
Bug #781498 reported by
Werner Jaeger
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
L2TP over IPsec VPN Manager |
Fix Released
|
Medium
|
Werner Jaeger |
Bug Description
when connecting ipsec auto --up is occasionally started before pluto is running or has added the connection. You then get an error 300 and in the connection information log you see something like this:
003 NAT-Traversal: Trying new style NAT-T
003 NAT-Traversal: ESPINUDP(1) setup failed for new style NAT-T family IPv4 (errno=19)
003 NAT-Traversal: Trying old style NAT-T
000 initiating all conns with alias='freeusvpn'
021 no connection named "XXXXXX"
[ERROR 300] 'IPsec' failed to negotiate or establish security associations
Changed in l2tp-ipsec-vpn: | |
importance: | Undecided → Medium |
assignee: | nobody → Werner Jaeger (werner-jaeger) |
status: | New → In Progress |
Changed in l2tp-ipsec-vpn: | |
milestone: | none → 1.0.0 |
Changed in l2tp-ipsec-vpn: | |
status: | In Progress → Fix Committed |
Changed in l2tp-ipsec-vpn: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think that there is a regression on this bug usng the last version 1.0.6