property 'Disable NAT Traversal' invalid or not supported

Bug #280926 reported by Martin von Gagern on 2008-10-09
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Undecided
Unassigned
Nominated for Gutsy by Eimann
Nominated for Hardy by Eimann
Nominated for Intrepid by wired

Bug Description

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.

Martin von Gagern (gagern) wrote :
Benny (bm-cage) wrote :
Download full text (4.4 KiB)

I could not connect to my vpnc at work through kubuntu Intrepid, all worked in Hardy before.

Thanks to this bug entry i got it to work works, however I had to delete in .kde/share/config/knetworkmanagerrc the problematic settings, so from

Type=vpn
Value_data=<map>\n <entry>\n <string>Disable NAT Traversal</string>\n <string>none</string>\n </entry>\n <entry>\n <string>Enable Single DES</string>\n <string>no</string>\n </entry>\n <entry>\n <string>IPSec ID</string>\n <string>ipsecclient</string>\n </entry>\n <entry>\n <string>IPSec gateway</string>\n ....

to

Type=vpn
Value_data=<map>\n <entry>\n <string>IPSec ID</string>\n <string>ipsecclient</string>\n </entry>\n <entry>\n <string>IPSec gateway</string>\n .....

So no longer the entries Disable NAT Traversal and Enable Single Des
With 'none' and 'no' my connection still did not come up. The error was the same as in the bug entry:

cristina@mccdell:~$ tail /var/log/syslog
Nov 2 19:00:57 mccdell NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections
Nov 2 19:00:57 mccdell NetworkManager: <info> VPN plugin state changed: 1
Nov 2 19:01:10 mccdell NetworkManager: <info> VPN plugin state changed: 3
Nov 2 19:01:10 mccdell NetworkManager: <info> VPN connection 'VPN UGent' (Connect) reply received.
Nov 2 19:01:10 mccdell NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'VPN UGent' failed to connect: 'property 'Disable NAT Traversal' invalid or not supported'.
Nov 2 19:01:10 mccdell NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.
Nov 2 19:01:10 mccdell NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Nov 2 19:01:10 mccdell NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Nov 2 19:01:22 mccdell NetworkManager: <debug> [1225648882.261584] ensure_killed(): waiting for vpn service pid 9125 to exit
Nov 2 19:01:22 mccdell NetworkManager: <debug> [1225648882.261927] ensure_killed(): vpn service pid 9125 cleaned up

after the change to the config file, all was ok:

Nov 2 19:05:01 mccdell NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'...
Nov 2 19:05:01 mccdell NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 9418
Nov 2 19:05:01 mccdell NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections
Nov 2 19:05:01 mccdell NetworkManager: <info> VPN plugin state changed: 1
Nov 2 19:05:16 mccdell NetworkMana...

Read more...

Hi,

applied the patch, recompiled and made new configuration - works fine here! Thank You!

Sebastian

Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.

Changed in knetworkmanager (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers