[feisty] no currently active network device, won't activate VPN

Bug #116274 reported by Joe Baker
18
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Low
Unassigned
network-manager-openvpn (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager-openvpn

My WiFI card shows up as eth1. In a profile where Eth0 (a true ethernet port) is down and wifi (eth1) is up I find when trying to engage an openvpn connection with Network-Manager that an error in /var/log/syslog reports:

no currently active network device, won't activate VPN

I'll reboot and try with Ethernet.

Thanks for saving me from having to execute openvpn from a shell with this GUI.

-Joe

Revision history for this message
Joe Baker (joebaker) wrote :

This problem appears to have healed itself. I've recently installed some updates. Although Network-Manager has been buggy for me, but I like the direction this application is moving toward.

Revision history for this message
srini (absrao) wrote :

I am having same issue.
I have a wireless dialup (Verizon EVDO), a network interface and a wireless interface.

Tried putting both regular network and wireless interace in roaming mode and EVDO dialed.
Tried disabling both regular network and wireless interface.
Tried with only network interface (connected to LAN).

Still the same thing shows up in syslog,,,
-------------------
 NetworkManager: <WARNING>^I nm_vpn_manager_activate_vpn_connection (): nm_vpn_manager_activate_vpn_connection(): no currently active network device, won't activate VPN.

-------------------

Revision history for this message
TomasHnyk (sup) wrote :
Revision history for this message
Àlex Magaz (rivaldi8) wrote :

I also have the same problem, but I found what was making it fail.

I have 2 wired ethernet cards, eth0 and eth1. eth0 is disconnected. eth1 is configured like this in /etc/network/interfaces:

auto eth1
iface eth1 inet dhcp
up /sbin/wondershaper eth1 984 302
down /sbin/wondershaper clear eth1

With this configuration, the NetworkManager icon appears as connected but no devices are listed when I click on it. If try to open a OpenVPN connection it fails. But after commenting the wondershaper lines, the two interfaces get listed in NetworkManager and VPN works.

Looking at NetworkManager logs it seems it's not enabling eth1 whith wondershaper lines.

Revision history for this message
JonPastore (jpastore-emdistro) wrote :

Also have this problem.

would updating the driver help? I have Dell M90 with the intel chip. I could probably switch out to a broadcom if I had to.

Is this a network manager problem? or a driver issue? I read somewhere that someone was able to turn on ndiswrapper and get it working. I followed the steps he posted online and got nowhere.

This seems to be something people are complaining about in many forums. I think this needs to be a high priority bug. This is critical to users outside the US who need to PPTP to their isp for internet access and need to so over their wifi and corp. users (like myself) who need it for work.

Revision history for this message
Philipp Kern (pkern) wrote :

The initiation of the VPN connection is not refused by the openvpn plugin but by network-manager itself.

Changed in network-manager-openvpn:
status: New → Invalid
Revision history for this message
Konrads Smelkovs (konrads-smelkovs) wrote :

I can only second the problem.
When ethernet interface is managed in "manual mode" (static IP), then the connection is not listed in network-manager and VPN is not instantiated.

kstest@ubu-gk-ks:/etc/openvpn$ Nov 21 09:56:47 ubu-gk-ks NetworkManager: <info> Will activate VPN connection 'queen eds', service 'org.freedesktop.NetworkManager.openvpn', user_name 'kstest', vpn_data 'connection-type / x509 / dev / tun / remote / 81.XXX.XXX.XXX / port / 1194 / proto / udp / servercert-insecure / no / ca / /home/kstest/ca.crt / cert / /home/kstest/gk-ks-test.crt / key / /home/kstest/gk-ks-test.key / comp-lzo / no / shared-key / / local-ip / / remote-ip / / username / / ta / /home/kstest/ta.key / ta-dir / 1', route '192.168.0.0/16'.
Nov 21 09:56:47 ubu-gk-ks NetworkManager: <WARN> nm_vpn_manager_activate_vpn_connection(): nm_vpn_manager_activate_vpn_connection(): no currently active network device, won't activate VPN.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager:
assignee: nobody → sourcercito
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
JonPastore (jpastore-emdistro) wrote : Re: [Bug 116274] Re: [feisty] no currently active network device, won't activate VPN

Honestly I had so many issues with network manager I decided to switch
to wicd. I'm testing vpn with now. The promise of 0.7.0 sounded great
but it's months over due and I need to be able to join wep wifi networks
and other wpa networks than my home one and it just wasn't happening
with netowkr manager...even post format and reinstall...

Jon Pastore, RHCE
EMD President
954.323.2513 [Office]
954.905.4302 [Fax]
954.937.7813 [Mobile]

The information in this email is intended only for the personal and
confidential use of the designated recipient above. If the reader of
this message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that
you have received this document in error, and that any review,
dissemination, distribution, or copying of the message is strictly
prohibited. If you are not the intended recipient, please contact the
sender immediately by reply e-mail and destroy all copies of the
original message.

On Thu, 2008-03-20 at 15:14 +0000, Basilio Kublik wrote:

> Hi there
> do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.
>
> Thanks in advance
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Basilio Kublik (sourcercito)
> Status: New => Incomplete
>

Changed in network-manager:
assignee: sourcercito → nobody
Revision history for this message
Basilio Kublik (sourcercito) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
Revision history for this message
Konrads Smelkovs (konrads-smelkovs) wrote :

Hello,

I can repeat my above statement on latest ubuntu:

May 21 15:07:43 talon NetworkManager: <info> Will activate VPN connection 'vid', service 'org.freedesktop.NetworkManager.openvpn', user_name 'konrads', vpn_data 'connectio
n-type / x509 / dev / tun / remote / 192.168.0.1 / port / 1194 / proto / udp / servercert-insecure / no / ca / /home/konrads/vpn keys/ca.crt / cert / /home/konrads/vpn keys
/talon.crt / key / /home/konrads/vpn keys/talon.key / comp-lzo / yes / shared-key / / local-ip / / remote-ip / / username / / cipher / BF-CBC / ta / /home/konrads/vpn k
eys/ta.key / ta-dir / 1', route ''.
May 21 15:07:43 talon NetworkManager: <WARN> nm_vpn_manager_activate_vpn_connection(): nm_vpn_manager_activate_vpn_connection(): no currently active network device, won't
activate VPN.

I suspect this is due to reasons staed before - manually configured network.

Revision history for this message
HWassermann (hwassermann) wrote :

Easy to reproduce in my case. Brand new install of Hardy with 2 network adapters - one WLAN and one Ethernet. I had the WLAN disabled (Enable wireless unchecked in the tray app) and not connected to an AP. That´s when I got this error. I tried the Ethernet adapter both in and out of roaming mode with the same effect.

After enabling WLAN and connecting to an access point, I got a step further -- authentication failure. I now suspect special characters in my name being the cause of the auth trouble, but that´s another story for another thread.

Changed in network-manager:
status: Invalid → New
Revision history for this message
Francois (zorgluf) wrote :

Hi,
I have just reproduced the same behaviour with network-manager-vpnc on hardy.
I have two network interfaces : eth0 (ethernet cable) and wlan0.
I configure both interface through network-manager GUI (no manual configuration), but each time I connect VPN through wlan0, I get :
Sep 9 09:30:24 IS202619 NetworkManager: <info> Will activate VPN connection 'XX', service 'org.freedesktop.NetworkManager.vpnc', user_name 'fv212846', vpn_data 'IPSec gateway / YYY.YYY.YYY.Y / IPSec ID / XXX / Xauth username / fv212846', route '132.166.0.0/16 / 132.167.0.0/16'.
Sep 9 09:30:24 IS202619 NetworkManager: <WARN> nm_vpn_manager_activate_vpn_connection(): nm_vpn_manager_activate_vpn_connection(): no currently active network device, won't activate VPN.

Oddly, when I plug a cable on eth0, whithout configuring the interface, everything works OK.

Revision history for this message
Alexander Sack (asac) wrote :

this should be fixed in 0.7 - which ships in intrepid. how devices are managed and vpn plugins use them has been mostly rewritten. If you see other issues with vpn plugins against 0.7, please open new bugs.

Changed in network-manager:
status: New → Fix Released
Revision history for this message
Konrads Smelkovs (konrads-smelkovs) wrote : Re: [Bug 116274] Re: [feisty] no currently active network device, won't activate VPN

Will there not be fixes for LTS?
--
Konrads Smelkovs
Applied IT sorcery.

On Tue, Sep 23, 2008 at 1:21 AM, Alexander Sack <email address hidden> wrote:

> this should be fixed in 0.7 - which ships in intrepid. how devices are
> managed and vpn plugins use them has been mostly rewritten. If you see
> other issues with vpn plugins against 0.7, please open new bugs.
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Fix Released
>
> --
> [feisty] no currently active network device, won't activate VPN
> https://bugs.launchpad.net/bugs/116274
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Iric (liuzhy-joy) wrote :

I still have this problem now . I have one WLAN and one Ethernet eth1.The WLAN is disabled, but when I connected VPN, I got:
Oct 2 10:27:21 TCiric NetworkManager: <info> Will activate VPN connection 'yumen', service 'org.freedesktop.NetworkManager.ppp_starter', user_name 'iric', vpn_data 'ppp-connection-type / pptp / pptp-remote / 10.20.116.7 / usepeerdns / yes / encrypt-mppe / no / encrypt-mppe-128 / yes / encrypt-mppe-stateful / yes / compress-mppc / no / compress-deflate / no / compress-bsd / no / ppp-lock / yes / ppp-auth-peer / yes / ppp-refuse-eap / yes / ppp-refuse-chap / no / ppp-refuse-mschap / no / mtu / 1416 / mru / 1416 / lcp-echo-failure / 10 / lcp-echo-interval / 10 / ppp-extra / / ppp-debug / no / usepeerdns-overtunnel / yes / routes / / use-routes / no', route ''.
Oct 2 10:27:21 TCiric NetworkManager: <WARN> nm_vpn_manager_activate_vpn_connection(): nm_vpn_manager_activate_vpn_connection(): no currently active network device, won't activate VPN.
Oct 2 10:27:21 TCiric NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Network is down

It seems to connect VPN through WLAN as well.

If you can help me ,please send me a Email. <email address hidden>
Thx

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.