Openswan won't connect after upgrading to 1:2.6.37-3+deb7u1

Bug #1304674 reported by wezlo on 2014-04-08
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openswan (Debian)

Bug Description

After upgrading to openswan 1:2.6.37-3+deb7u1 I can no longer connect to my openswan vpn.

The errors in auth.log are:

"sending notification INVALID_PAYLOAD_TYPE"
"message ignored because it contains an unknown or unexpected payload type (ISAKMP_NEXT_SAK) at the outermost level"

Downgrading to openswan 2.6.37 allows me to establish a connection, but the I miss the updated openssl packages which are supposed to fix the heartbeat bug.

peter green (plugwash) wrote :

Unfortunately i'm not sure there is much we can do here, if you can work out what is going wrong and supply a patch then we may be able to apply it but we don't have the resources to debug this sort of thing ourselves and openswan in debian seems pretty close to dead.

Rebecca Palmer (rebecca-palmer) wrote :

> openswan in debian seems pretty close to dead
It has been proposed for removal:

The suggested replacement is strongswan, which is available in Raspbian.

peter green (plugwash) wrote :

Well I sent an email about this issue to debian and got the following reply from Yves-Alexis Perez

>That looks like
>which I need to take care of.

Adding a reference to that bug.

Changed in openswan (Debian):
status: Unknown → New
Changed in openswan (Debian):
status: New → Fix Released
Changed in openswan (Debian):
status: Fix Released → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.