[Bug 280926] [NEW] property 'Disable NAT Traversal' invalid or not supported

Martin von Gagern martin.vgagern at gmx.net
Thu Oct 9 20:04:19 UTC 2008


Public bug reported:

Binary package hint: knetworkmanager

This is Intrepid beta with these packages:
network-manager-kde 1:0.7svn864988-0ubuntu1
network-manager-vpnc 0.7~~svn20080928t225540-0ubuntu1
vpnc 0.5.1r275-1ubuntu1

Trying to connect to a vpn using network-manager-vpnc failed without any
error message in knetworkmanager. Looking at /var/log/daemon.log I found
this:

NetworkManager: <info>  Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... 
NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 8161 
NetworkManager: <info>  VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections 
NetworkManager: <info>  VPN plugin state changed: 1 
NetworkManager: <info>  VPN plugin state changed: 3 
NetworkManager: <info>  VPN connection 'ConnectionName' (Connect) reply received. 
NetworkManager: <WARN>  nm_vpn_connection_connect_cb(): VPN connection 'ConnectionName' failed to connect: 'property 'Disable NAT Traversal' invalid or not supported'. 
NetworkManager: <debug> [1223576517.524329] ensure_killed(): waiting for vpn service pid 8161 to exit 
NetworkManager: <debug> [1223576517.524943] ensure_killed(): vpn service pid 8161 cleaned up 

Looking at the sources for all the packages in volved, I found that
network-manager-vpnc doesn't mention "Disable NAT Traversal" at all, and
vpnc only has it in its translations. network-manager-kde is the only
package with the string included verbatim in its active sources. So I
take it that knetworkmanager is trying to talk to a pervious incarnation
of vpnc, and that the current version no longer has this option.

Looking at the vpnc svn repository, this option was last seen in the
0.3.3 release of vpnc, dating from 2005. It was removed from trunk in
r98. An online diff is availavle from http://bazaar.launchpad.net/~vcs-
imports/vpnc/trunk/revision/94 . I guess the strict options checking was
added more recently.

The correct replacement string would probably be "NAT Traversal Mode none" for the case of disabled NAT traversal and "NAT Traversal Mode natt" for the default enabled NAT traversal. A dropdown to select values from might provide more flexibility, but also make it harder for novice users to understand. Once that string is fixed, knetworkmanager will next complain about "Enable Single DES", for which the values "yes" and "no" are expected, not "1" and "0":
'invalid boolean property 'Enable Single DES' (not yes or no)'

Users who want to work around this issue might edit their
.kde/share/config/knetworkmanagerrc manually. For inclusion into ubuntu
as well as upstream sources, I'll also attach a patch. If you patch your
network-manager-kde or install an official Ubuntu package with this fix
in place, you'll have to remove and recreate your vpnc configuration, as
it seems the old settings won't go away even when you edit an existing
configuration.

** Affects: knetworkmanager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
property 'Disable NAT Traversal' invalid or not supported
https://bugs.launchpad.net/bugs/280926
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.




More information about the kubuntu-bugs mailing list