Bugzilla – Bug 439742
VPNC did not work with NetworkManager-kde
Last modified: 2016-04-15 09:15:52 UTC
Config a vpnc connection works Establish a connection did not work. No reaction after clicking on the entry. NetworkManager log: Oct 27 15:25:30 linux-1c2m NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Oct 27 15:25:30 linux-1c2m NetworkManager: <WARN> nm_vpn_service_daemon_exec(): VPN service 'org.freedesktop.NetworkManager.vpnc': could not launch the VPN service. error: (8) Failed to execute child process "/usr/lib/NetworkManager-vpnc/nm-vpnc-service" (No such file or directory). Oct 27 15:25:30 linux-1c2m NetworkManager: <WARN> impl_manager_activate_connection(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/7 failed to activate: (3) Failed to execute child process "/usr/lib/NetworkManager-vpnc/nm-vpnc-service" (No such file or directory)
Johann, The rpm package's problem, the service path is wrong, I've already fixed. And it already in Beta4. http://download.opensuse.org/repositories/GNOME:/Factory/openSUSE_Factory/i586/NetworkManager-vpnc-0.7.0.r4209-7.3.i586.rpm http://download.opensuse.org/repositories/GNOME:/Factory/openSUSE_Factory/i586/NetworkManager-vpnc-gnome-0.7.0.r4209-7.3.i586.rpm Would you mind try these packages?
It still did not work. NetworkManager log: Nov 5 09:09:35 t500 NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/4 failed to activate (timeout): (0) Connection was not provided by any settings service This packages are not in the main Factory reposotory. Need i a update for the vpnc-kde package?
(In reply to comment #2 from Johann-Nikolaus Andreae) > It still did not work. > NetworkManager log: > Nov 5 09:09:35 t500 NetworkManager: <WARN> wait_for_connection_expired(): > Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/4 failed to > activate (timeout): (0) Connection was not provided by any settings service > This packages are not in the main Factory reposotory. > Need i a update for the vpnc-kde package? Do you use the KDE desktop? if so, install it. Would you attach more log when run "NetworkManager --no-daemon"? Of course kill the process first, then send me back your log.
yes i use kde. there is no new package for kde available. NetworkManager output (last line is vpnc) NetworkManager: <info> starting... -- Error received: File exists -- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC> sequence-nr=1225901509 pid=4203512 NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4237_rfkill_5100AGN_wlan NetworkManager: <info> eth0: driver is 'e1000e'. NetworkManager: <info> Found new Ethernet device 'eth0'. NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1c_25_97_ef_46 NetworkManager: <info> wlan0: driver is 'iwlagn'. NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). NetworkManager: <info> Found new 802.11 WiFi device 'wlan0'. NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_21_5d_a8_de_ba NetworkManager: <WARN> killswitch_getpower_reply(): Error getting killswitch power: Method "GetPower" with signature "" on interface "org.freedesktop.Hal.Device.KillSwitch" doesn't exist . NetworkManager: <info> (eth0): device state change: 1 -> 2 NetworkManager: <info> (eth0): bringing up device. NetworkManager: <info> (eth0): preparing device. NetworkManager: <info> (eth0): deactivating device (reason: 2). NetworkManager: <info> (wlan0): device state change: 1 -> 2 NetworkManager: <info> (wlan0): bringing up device. NetworkManager: <info> (wlan0): preparing device. NetworkManager: <info> (wlan0): deactivating device (reason: 2). NetworkManager: <info> (wlan0): device state change: 2 -> 3 NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2. NetworkManager: <info> (eth0): carrier now ON (device state 2) NetworkManager: <info> (eth0): device state change: 2 -> 3 NetworkManager: <info> Activation (eth0) starting connection 'Auto eth0' NetworkManager: <info> (eth0): device state change: 3 -> 4 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (eth0): device state change: 4 -> 5 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: <info> (eth0): device state change: 5 -> 7 NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0: unknown hardware address type 801 NetworkManager: <info> dhclient started with pid 9211 wmaster0: unknown hardware address type 801 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit Listening on LPF/eth0/00:1c:25:97:ef:46 Sending on LPF/eth0/00:1c:25:97:ef:46 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 141.22.27.2 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 141.22.27.2 bound to 141.22.26.77 -- renewal in 1712 seconds. NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... NetworkManager: <info> address 141.22.26.77 NetworkManager: <info> prefix 23 (255.255.254.0) NetworkManager: <info> gateway 141.22.26.1 NetworkManager: <info> hostname 'andrea_j' NetworkManager: <info> nameserver '141.22.192.100' NetworkManager: <info> nameserver '141.22.192.101' NetworkManager: <info> nameserver '141.22.192.102' NetworkManager: <info> domain name 'cpt.haw-hamburg.de' NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... NetworkManager: <info> (eth0): device state change: 7 -> 8 NetworkManager: <debug> [1225901519.021484] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' NetworkManager: <debug> [1225901519.036801] write_to_netconfig(): Writing to netconfig: INTERFACE='eth0' NetworkManager: <debug> [1225901519.037103] write_to_netconfig(): Writing to netconfig: DNSSEARCH='cpt.haw-hamburg.de cpt.haw-hamburg.de' NetworkManager: <debug> [1225901519.037340] write_to_netconfig(): Writing to netconfig: DNSSERVERS='141.22.192.100 141.22.192.101 141.22.192.102' NetworkManager: <info> Clearing nscd hosts cache. NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS. NetworkManager: <info> Activation (eth0) successful, device activated. NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ... NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/4 failed to activate (timeout): (0) Connection was not provided by any settings service
Tambet, I'm not found what's caused this information, ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ... So is it the reason that the netconfig run failed or not return the right value?
I don't know, reassigning the info provider.
I copy the /etc/resolv.conf.netconfig to /etc/resolv.conf and restart the networl (rcnetwork restart). It still did not work. I found out that it coud be a gerneral problem of the NetworkMangager. Setting up IP manualy still did not work (bug #439413). yesterday i try to conect to a wireless WEP network. the same massage in the NetworkManager log: Nov 10 09:50:56 t500 NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/5 failed to activate (timeout): (0) Connection was not provided by any settings service How to reassign the info provider?
Johann, You are the info provider, when you provide information, just select "Leave as ASSIGNED". And do you try to use the vpnc in terminal connecting the VPN gateway? Does it connect successfully?
Ok sorry i did not notice that i was not inforequest for me. Yes run vpnc on the console works.
Johann, From the information in Comment #2, I'm not found something like this: Starting VPN service 'org.freedesktop.NetworkManager.vpnc'.. So would you mind kill the NetworkManager and run with "--no-daemon" again? After the connection is ok, click the VPN connections for selecting what you wanna connect, after this click the log on screen will be useful, and till it failed information outing. Thanks!
If i click on the vpn connection i get on the follogwing message: NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/4 failed to activate (timeout): (0) Connection was not provided by any settings service No more information what is wrong. The same massage i get if i try to set a IP manualy or connect to a encryted wlan (current only wep tested).
Johann, Very weird, so just attach your /var/log/message which you have done the vpn connection operation.
There is no output at /var/log/message if i try to connect via NetworkManager Connect via vpnc i get the following output: Nov 11 10:21:07 t500 kernel: tun: Universal TUN/TAP device driver, 1.6 Nov 11 10:21:07 t500 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Nov 11 10:21:07 t500 kernel: tun0: Disabled Privacy Extensions
(In reply to comment #13 from Johann-Nikolaus Andreae) > There is no output at /var/log/message if i try to connect via NetworkManager > Connect via vpnc i get the following output: > > Nov 11 10:21:07 t500 kernel: tun: Universal TUN/TAP device driver, 1.6 > Nov 11 10:21:07 t500 kernel: tun: (C) 1999-2004 Max Krasnyansky > <maxk@qualcomm.com> > Nov 11 10:21:07 t500 kernel: tun0: Disabled Privacy Extensions > So would you mind upload the /var/log/message file?
Created attachment 251523 [details] /var/log/messages
Isnt't it related to this? https://bugzilla.novell.com/show_bug.cgi?id=445153
no in my case vpnc works only via NetworkManager (KDE) not.
I've tried it with radius and local users too. With and without split tunnelling but neither worked. I use simple IPSec PSK with Xauth. What are your setting?
I use the comandline options --gateway, --id and --username with group and userpassword.
Johann, I doubt it relate to your NetworkManager's service, where is your nm-vpnc-service? Just use the "whereis nm-vpnc-service". Does it same with program key in "/etc/NetworkManager/VPN/nm-vpnc-service.name"?
yes it is. nm-vpnc-service: /usr/lib/nm-vpnc-service [VPN Connection] name=vpnc service=org.freedesktop.NetworkManager.vpnc program=/usr/lib/nm-vpnc-service
Johann, So I've no idea about this issue, could you assign me a temp account to connect the vpn server? I just wanna reproduce this issue in my environment so that I could debug it. Could you provide any help? Thanks!
No i did not can give you access to the vpn. it is the vpn of the university. I have found the a problem way knetworkmanager did not try to establish the connection. It is kded4. It blocks the networkmanager. I have found it out traying to use cnetworkmanager to establish a wlan- connection. :~> cnetworkmanager -C HAW-WLAN --unprotected cnetworkmanager 0.7.1 - Command Line Interface for NetworkManager Could not provide settings service, another applet is running knetworkmanager is terminated. Terminating the kde session an tray again. The "running applet" is terminated i get a differet errormassage from cnetworkmanager. Starting kde again. terminating all kde-demons that coud have access to the networkmanger. After killing kded4 the connection to wlan with knetoworkmanager work. Trayin the vpnc connection i get the following NetworkManager log output: Nov 19 16:57:51 t500 NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.vpnc'... Nov 19 16:57:51 t500 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 5726 Nov 19 16:57:51 t500 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections Nov 19 16:57:51 t500 NetworkManager: <info> VPN plugin state changed: 1 Nov 19 16:57:51 t500 NetworkManager: <info> VPN plugin state changed: 3 Nov 19 16:57:51 t500 NetworkManager: <info> VPN connection 'HAW-Home' (Connect) reply received. Nov 19 16:57:51 t500 NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'HAW-Home' failed to connect: 'property 'Disable NAT Traversal' invalid or not supported'. Nov 19 16:57:51 t500 NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active. The property 'Disable NAT Traversal' is not checked in the vpnc settings.
(In reply to comment #23 from Johann-Nikolaus Andreae) > Trayin the vpnc connection i get the following NetworkManager log output: > Nov 19 16:57:51 t500 NetworkManager: <info> Starting VPN service > 'org.freedesktop.NetworkManager.vpnc'... > Nov 19 16:57:51 t500 NetworkManager: <info> VPN service > 'org.freedesktop.NetworkManager.vpnc' started > (org.freedesktop.NetworkManager.vpnc), PID 5726 > Nov 19 16:57:51 t500 NetworkManager: <info> VPN service > 'org.freedesktop.NetworkManager.vpnc' just appeared, activating connections > Nov 19 16:57:51 t500 NetworkManager: <info> VPN plugin state changed: 1 > Nov 19 16:57:51 t500 NetworkManager: <info> VPN plugin state changed: 3 > Nov 19 16:57:51 t500 NetworkManager: <info> VPN connection 'HAW-Home' > (Connect) reply received. > Nov 19 16:57:51 t500 NetworkManager: <WARN> nm_vpn_connection_connect_cb(): > VPN connection 'HAW-Home' failed to connect: 'property 'Disable NAT Traversal' > invalid or not supported'. > Nov 19 16:57:51 t500 NetworkManager: <WARN> connection_state_changed(): Could > not process the request because no VPN connection was active. > > The property 'Disable NAT Traversal' is not checked in the vpnc settings. > Tamás already give me an vpn account for testing, but not certificate method. And what's your NetworkManager-vpnc ang NetworkManager-vpnc-gnome version? From the source code r4209 and r4274, not found any "Disable NAT Traversal" keyword in source file.
Oh, you not use the nm-applet, it should be the knetworkmanager's problem. what's your knetworkmanager's version?
Should be NetworkManager-vpnc-kde or NetworkManager-vpnc-kde4? What version of these package?
NetworkManger 0.7.0.r4274-2.1 NetworkManager-vpnc 0.7.0.r4274-1.4 NetworkManager-kde 0.7r848570-21.1 NetworkManager-vpnc-kde 0.7r848570-21.1 NetworkManager.kde4 0.7-5.2 I use the kde3 vorsion. NetworkManager kde4 current did not work. After the last (bata4 -> beta5) update thare is a emty widget.
Review the NetworkManager-kde code, the "Disable NAT Traversal" not support any more. Should use "NAT Traversal Mode", and the value should be "none", "natt" or "cisco-udp". Reassign to Helmut.
Hi guys. For everyday activities we use certificate based IPSec VPN, but vpnc does not support X509 certificates, AFAIK. Or does this new version? I can convert this test account to X509-based if you want to. BTW, KDE4's networkmanager is really unusable yet.
I have the same problem with NetworkManager-kde and NetworkMangager-vpnc-kde on openSUSE 11.1 Final. NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/6 failed to activate (timeout): (0) Connection was not provided by any settings service I get a similar error when I try to establish a connection via my Vodafone UMTS card: NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/8 failed to activate (timeout): (0) Connection was not provided by any settings service So this does not seem to be a VPNC specific problem...
I have the same problem with openSUSE 11.1 GM. From /var/log/NetworkManager I see Jan 11 19:38:01 notebook NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'uni-wuppertal-extern' failed to connect: 'property 'Disa ble NAT Traversal' invalid or not supported'. which corresponds to comment 28.
Fix submitted to Factory.
Will it also be fixed in openSUSE 11.1?
Sorry, on more question: Do you still need the test account?
(In reply to comment #33) > Will it also be fixed in openSUSE 11.1? I would like to collect some more KNM fixes first before issuing an online update. (In reply to comment #34) > Sorry, on more question: Do you still need the test account? No, thanks.
>> Will it also be fixed in openSUSE 11.1? >I would like to collect some more KNM fixes first before issuing an online >update. Thank you for the development work, and the quick reply. May I suggest you to take a look at this issue, which may be even more serious than this one: https://bugzilla.novell.com/show_bug.cgi?id=444740 >> Sorry, on more question: Do you still need the test account? >No, thanks. Anyway, I'll leave it open in case of an unexpected need.
I've closed the account. Just ask me if you need it again.
KNetworkManager for KDE3 is not maintained any longer. Therefore I resolve all bugs that are still open as WONTFIX without looking at each single bug report. If this bug deals already with KDE4 and is still in progress, then please apologize the mistake and feel free to reopen it.
This is an autogenerated message for OBS integration: This bug (439742) was mentioned in https://build.opensuse.org/request/show/4884 Factory / NetworkManager-kde