After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 524105 - Please provide information on errors
Please provide information on errors
Status: RESOLVED DUPLICATE of bug 563159
Product: NetworkManager
Classification: Platform
Component: VPN: vpnc
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
: 538448 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-24 12:06 UTC by Priit Laes (IRC: plaes)
Modified: 2009-05-12 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Priit Laes (IRC: plaes) 2008-03-24 12:06:18 UTC
I have vpnc VPN connection I would like to use, but it doesn't work somehow (although I know what is the reason there is no visible information for regular desktop user)

From message log:
Mar 24 13:47:19 chi NetworkManager: <info>  VPN Activation (xxx) Stage 1 of 4 (Connection Prepare) scheduled...
Mar 24 13:47:19 chi NetworkManager: <info>  VPN Activation (xxx) Stage 1 of 4 (Connection Prepare) ran VPN service daemon org.freedesktop.NetworkManager.vpn
c (PID 8621)
Mar 24 13:47:19 chi NetworkManager: <info>  VPN Activation (xxx) Stage 1 of 4 (Connection Prepare) complete.
Mar 24 13:47:19 chi NetworkManager: <info>  VPN Activation (xxx) Stage 2 of 4 (Connection Prepare Wait) scheduled...
...SNIP...
Mar 24 13:47:21 chi NetworkManager: <info>  VPN Activation (xxx) Stage 2 of 4 (Connection Prepare Wait) scheduled...
Mar 24 13:47:21 chi NetworkManager: <info>  VPN Activation (xxx) Stage 2 of 4 (Connection Prepare Wait) waiting...
Mar 24 13:47:21 chi NetworkManager: <info>  VPN Activation (xxx) failed.
Mar 24 13:47:21 chi NetworkManager: <WARN>  nm_vpn_service_stop_connection(): (VPN Service org.freedesktop.NetworkManager.vpnc): could not stop connection 'xxx' because service was 2.

Now, when starting vpnc from command line:

chi vpnc # vpnc xxx
vpnc was built without openssl: Can't do hybrid or cert mode.

Also return code is 1

Now it would be nice to see that information in either syslog or error dialog.
Comment 1 Dan Williams 2008-11-14 00:31:06 UTC
*** Bug 538448 has been marked as a duplicate of this bug. ***
Comment 2 Priit Laes (IRC: plaes) 2009-04-23 05:11:35 UTC
Well, second time I stumbled on this :)

This is the networkmanager's connection sharing feature... 
From the UI everything seems like it works flawlessly, but in the background we can see this:

Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlan1 --protocol tcp --destination-port 53 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlan1 --protocol udp --destination-port 53 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlan1 --protocol tcp --destination-port 67 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlan1 --protocol udp --destination-port 67 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert FORWARD --in-interface wlan1 --jump REJECT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert FORWARD --out-interface wlan1 --jump REJECT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert FORWARD --in-interface wlan1 --out-interface wlan1 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert FORWARD --source 10.42.43.0/255.255.255.0 --in-interface wlan1 --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table filter --insert FORWARD --destination 10.42.43.0/255.255.255.0 --out-interface wlan1 --match state --state ESTABLISHED,RELATED --jump ACCEPT
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.
Apr 23 08:00:39 chi NetworkManager: <info>  Executing: /sbin/iptables --table nat --insert POSTROUTING --source 10.42.43.0/255.255.255.0 --destination ! 10.42.43.0/255.255.255.0 --jump MASQUERADE
Apr 23 08:00:39 chi NetworkManager: <info>  ** Command returned exit status 3.

Comment 3 Dan Williams 2009-05-12 22:56:44 UTC

*** This bug has been marked as a duplicate of 563159 ***