Bug 722655 - OpenVPN :: couldn't determine device driver; ignoring...
Summary: OpenVPN :: couldn't determine device driver; ignoring...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-openvpn
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-16 08:26 UTC by Sigmarsson
Modified: 2012-08-07 16:02 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-07 16:02:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sigmarsson 2011-07-16 08:26:33 UTC
Description of problem:

I have set loglevel of NetworkManager to DEBUG to exact more information why nm-openvpn-service-openvpn-helper is unable to accomplish network interface configuration. Actually the device (tap0) created and would be available for further operations (ifup, route table update etc.) but somehow it never happens. 

I cannot figure out actually the "call stack" among several external program calls, however I v found the particular error gets printed out from nm-udev-manager.c :: /sys/devices/virtual/net/tap0: couldn't determine device driver; ignoring..., which led me to the global function call, see beneath. 

Does any1 have idea why const gchar * g_udev_device_get_driver (GUdevDevice *device);
routine call fails and in the end I am getting /sys/devices/virtual/net/tap0: couldn't determine device driver; ignoring... error message in the log, since *device is NULL?
As far as I am concerned the device_creator () invokes somehow the global routine above and if it is so, the device_creator() does not succeed anything and hands over the NULL pointer. Has anyone idea ?





Version-Release number of selected component (if applicable):
NetworkManager-openvpn-0.8.999-1.fc15.i686

How reproducible:


Steps to Reproduce:
1. Open NM GUI, enter gateway + certificates path + key + use LZO + use TAP
2. Save
3. VPN Conenctions -> Connect...
  
Actual results:

Here is the log :

Jun 13 19:58:49 xfce nm-openvpn[1463]: TUN/TAP device tap0 opened
Jun 13 19:58:49 xfce nm-openvpn[1463]: /usr/libexec/nm-openvpn-service-openvpn-helper tap0 1500 1574   init
Jun 13 19:58:50 xfce NetworkManager[648]: <debug> [1307987930.5748] [nm-udev-manager.c:586] handle_uevent(): UDEV event: action 'add' subsys 'net' device 'tap0'
Jun 13 19:58:50 xfce NetworkManager[648]: <warn> /sys/devices/virtual/net/tap0: couldn't determine device driver; ignoring...
Jun 13 19:58:50 xfce NetworkManager[648]: <warn> VPN plugin failed: 2
Jun 13 19:58:50 xfce nm-openvpn[1463]: script failed: external program exited with error status: 1
Jun 13 19:58:50 xfce nm-openvpn[1463]: Exiting

Expected results:


Additional info:

F15 runs as VM on a Windows 7

Comment 1 Nick Lamb 2011-07-18 11:48:57 UTC
I see the same problem, on real hardware (a Thinkpad laptop) and with Fedora 14

However for me this is intermittent. I believe the crucial lines from your log (which I also see) are


Jun 13 19:58:49 xfce nm-openvpn[1463]: /usr/libexec/nm-openvpn-service-openvpn-helper tap0 1500 1574   init
Jun 13 19:58:50 xfce nm-openvpn[1463]: script failed: external program exited
with error status: 1

It appears nm-openvpn attempts to execute nm-openvpn-service-openvpn-helper and this latter program gives exit code 1. The cause of THAT failure isn't logged and thus we can only speculate about it.

One way forward may be to rename /usr/libexec/nm-openvpn-service-openvpn-helper and insert a shell script in its place which can run it under a debugger. If the helper emitted some more helpful message we could use ferror (frysk) to debug.

Comment 2 Sigmarsson 2011-07-20 20:38:51 UTC
Hi Nick,

Yeah that could be a workaround as well to get more information. As I wrote earlier I fetched the source code and found the error message in nm-udev-manager.c source file which is gets printed in our log just because an other function passes a NULL pointer to g_udev_device_get_driver()

Here you can see my former post with a little more snippet. 

I did not debug through the entire call stack since I may not fix it after all.
The helper of the NetworkManager is somehow miserable, since it should just invoke a dhcp client and insert a new entry in the route table. 

Try to export your OpenVPN configuration into a file and call openvpn <your_config> hopefully you get your tap device and you can get configured by dhclient.

Sigmarsson


http://forums.fedoraforum.org/showthread.php?t=265476
http://forums.fedoraforum.org/showthread.php?t=265021

Comment 3 Sigmarsson 2011-10-01 23:12:49 UTC
Hello,

Can anyone maybe explain what parameters nm-openvpn-service-openvpn-helper expects ? Is the entire interface configuration unsuccessful due lldpad ? I think some more parameters should be given for the helper tool yet.

Kind regards,
Sigmarsson
 


Oct  2 01:01:18 xfce nm-openvpn[2647]: /usr/libexec/nm-openvpn-service-openvpn-helper tap0 1500 1574   init
Oct  2 01:01:18 xfce NetworkManager[745]: <debug> [1317510078.961972] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 5 flags 0x1002
Oct  2 01:01:18 xfce lldpad[885]: evb_ifdown:port tap0 remove failed
Oct  2 01:01:18 xfce lldpad[885]: vdp_ifdown:tap0 vdp data remove failed
Oct  2 01:01:19 xfce NetworkManager[745]: <warn> VPN plugin failed: 2
Oct  2 01:01:19 xfce nm-openvpn[2647]: script failed: external program exited with error status: 1
Oct  2 01:01:19 xfce nm-openvpn[2647]: Exiting

Comment 4 Fedora End Of Life 2012-08-07 16:02:33 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.