Comment 27 for bug 300628

Revision history for this message
Sebastian Bator (eremit7) wrote :

I tested the Package in a natty Virtual Machine and got the same Error as with command line vpnc. Both abort with 'isakmp length does not match packet length: isakmp = 1947 != datalen = 1458'. The vpnc on the maverick host works fine (and I simply copied the configuration files). So could be Virtualbox or the natty package vpnc. It seem that nm-vpnc invokes vpnc right.

Here is the end of what NetworkManager started with 'VPNC_DEBUG=1' saws:

 receiving: <========================
 [2011-04-03 17:39:11]

S4.4 AM_packet2
 [2011-04-03 17:39:11]
   BEGIN_PARSE
   Recieved Packet Len: 1458
   i_cookie: ade3a358 2b1f1d07
   r_cookie: 8574e238 3e84b0a5
   payload: 01 (ISAKMP_PAYLOAD_SA)
   isakmp_version: 10
   exchange_type: 04 (ISAKMP_EXCHANGE_AGGRESSIVE)
   flags: 00
   message_id: 00000000
   len: 0000079b
   isakmp length does not match packet length: isakmp = 1947 != datalen = 1458
/usr/sbin/vpnc: response was invalid [1]: (ISAKMP_N_UNEQUAL_PAYLOAD_LENGTHS)(30)
NetworkManager[2157]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)

** (nm-vpnc-service:2216): WARNING **: <WARN> vpnc_watch_cb(): vpnc exited with error code 1

NetworkManager[2157]: <warn> VPN plugin failed: 1
NetworkManager[2157]: <info> VPN plugin state changed: 6
NetworkManager[2157]: <info> VPN plugin state change reason: 0
NetworkManager[2157]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active.
NetworkManager[2157]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
NetworkManager[2157]: <info> VPN service 'vpnc' disappeared