Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
FedoraForum Search

Forgot Password? Join Us!

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 18th June 2011, 09:48 PM
Sigmarsson Offline
Registered User
 
Join Date: Jun 2011
Posts: 20
linuxchrome
OpenVPN :: couldn't determine device driver; ignoring...

Hello,

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 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 know if RedHat issue has been opened for such NetworkManager bug ?


Does any1 have idea why
Code:
const gchar *
g_udev_device_get_driver (GUdevDevice *device)
{
  g_return_val_if_fail (G_UDEV_IS_DEVICE (device), NULL);
  return udev_device_get_driver (device->priv->udevice);
}
this 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 ?


Sigmarsson





Code:
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
Reply With Quote
  #2  
Old 12th June 2012, 08:59 PM
Sigmarsson Offline
Registered User
 
Join Date: Jun 2011
Posts: 20
linuxchrome
Re: OpenVPN :: couldn't determine device driver; ignoring...

Hello again,

Today I attempted to establish a connection over TAP again, without any success, since the "helper" tool still unable to configure the tap0 interface. This is now a F17 (Beefy Miracle) but cannot overcome this :

Quote:
Jun 12 21:31:28 xfce nm-openvpn[3153]: TUN/TAP device tap0 opened
Jun 12 21:31:28 xfce nm-openvpn[3153]: /usr/libexec/nm-openvpn-service-openvpn-helper tap0 1500 1553 init
Jun 12 21:31:29 xfce NetworkManager[519]: <warn> VPN plugin failed: 2
Jun 12 21:31:29 xfce nm-openvpn[3153]: WARNING: Failed running command (--up/--down): external program exited with error status: 1
Jun 12 21:31:29 xfce nm-openvpn[3153]: Exiting
Jun 12 21:31:29 xfce udevd[337]: specified group 'plugdev' unknown
Jun 12 21:31:29 xfce avahi-daemon[529]: Withdrawing workstation service for tap0.
Jun 12 21:31:29 xfce NetworkManager[519]: <debug> [1339529489.37201] [nm-netlink-monitor.c:163] link_msg_handler(): netlink link message: iface idx 11 flags 0x1002
Jun 12 21:31:29 xfce NetworkManager[519]: <warn> VPN plugin failed: 1
Jun 12 21:31:29 xfce NetworkManager[519]: <info> VPN plugin state changed: stopped (6)
Jun 12 21:31:29 xfce NetworkManager[519]: <info> VPN plugin state change reason: 0
Has any1 idea how I could verbose log from the "helper" ?
Reply With Quote
  #3  
Old 12th June 2012, 11:07 PM
Sigmarsson Offline
Registered User
 
Join Date: Jun 2011
Posts: 20
linuxchrome
Re: OpenVPN :: couldn't determine device driver; ignoring...

Actually what I have just detected is that on the router I can direct the VPN server to specify a "Client address pool" if DHCP disabled. I can specify an address range from which an address will be taken.
As you can see beneath the log (.message.log attached), the "helper" tool now succeeds at interface initialization ! But right now for some reason my routing table is ****ed up, however I thought it is maintained by the "helper" when DHCP is not used.

Can any1 read between the lines ?
Attached Files
File Type: log .messages.log (13.0 KB, 22 views)
Reply With Quote
  #4  
Old 13th June 2012, 10:22 PM
Sigmarsson Offline
Registered User
 
Join Date: Jun 2011
Posts: 20
linuxchrome
Re: OpenVPN :: couldn't determine device driver; ignoring...

There is a successful connection with tunneling (TUN) but the "helper" tool is unable to restart tun0 ! See log :


Quote:
Jun 13 19:41:56 xfce nm-openvpn[9746]: Preserving previous TUN/TAP instance: tun0
Jun 13 19:41:56 xfce nm-openvpn[9746]: /usr/libexec/nm-openvpn-service-openvpn-helper tun0 1500 1522 10.8.0.6 10.8.0.5 restart
Jun 13 19:41:56 xfce NetworkManager[538]: <warn> VPN plugin failed: 2
Jun 13 19:41:56 xfce nm-openvpn[9746]: WARNING: Failed running command (--up/--down): external program exited with error status: 1
Jun 13 19:41:56 xfce nm-openvpn[9746]: Exiting
1. Do you know why ?
2. Do you know where I can specify the "keep alive" parameter in the network manager OpenVPN plugin ?
Reply With Quote
  #5  
Old 16th June 2012, 04:36 PM
Sigmarsson Offline
Registered User
 
Join Date: Jun 2011
Posts: 20
linuxchrome
Re: OpenVPN :: couldn't determine device driver; ignoring...

This is now the current routing table :

Quote:
[sigmarsson@xfce ~]$ ip route
default via 192.168.233.2 dev p3p2 proto static
10.8.0.1 via 10.8.0.5 dev tun0 proto static
10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6
172.17.229.0/24 via 10.8.0.5 dev tun0 proto static
192.168.233.0/24 dev p3p2 proto kernel scope link src 192.168.233.137
213.16.112.195 via 192.168.233.2 dev p3p2 proto static
... and the interfaces after VPN connection :

Quote:
[sigmarsson@xfce ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p3p2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:0c:29:6f:b0:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.233.137/24 brd 192.168.233.255 scope global p3p2
inet6 fe80::20c:29ff:fe6f:b0ad/64 scope link
valid_lft forever preferred_lft forever
7: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100
link/none
inet 10.8.0.6 peer 10.8.0.5/32 brd 10.8.0.6 scope global tun0
So why isn't 172.17.229.13 is unavailable ?


Quote:
[sigmarsson@xfce ~]$ ping 172.17.229.13
PING 172.17.229.13 (172.17.229.13) 56(84) bytes of data.
ping: sendmsg: Network is unreachable
^C
--- 172.17.229.13 ping statistics ---
21 packets transmitted, 0 received, 100% packet loss, time 20075ms
Reply With Quote
Reply

Tags
determine, device, driver, ignoring, openvpn

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
device driver help thelonesquirrel Using Fedora 2 27th February 2009 03:01 AM
How to determine which RHEL driver to use in fedora? marcp Hardware & Laptops 3 10th May 2008 04:20 PM
Determine ATI Driver Version for Fedora 8? guizhou_donkey Hardware & Laptops 2 2nd September 2007 01:40 PM
Can't determine PATCHLEVEL for making nvidia driver? Techokami Hardware & Laptops 0 24th July 2005 06:23 PM
ignoring a USB device smp64 Using Fedora 0 26th December 2004 05:38 PM


Current GMT-time: 06:53 (Saturday, 25-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat