OpenVPN client does not recognize WLAN connections

Bug #347788 reported by firebird
2
Affects Status Importance Assigned to Milestone
openvpn (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: openvpn

Hi folks!
This seems to be a common sight according to several threads i found on google, and btw. since several Ubuntu versions:
OpenVPN client connects perfectly as long as there is a cable attached to the computer.
If you try to use the WLAN connection that doesn't work.
According to OpenVPN's documentation the operation system should take care of the selection of connections,
and basically this works for almost every application, like for example Firefox.
Unfortunately it doesn't for OpenVPN.
Please fix this as soon as you can as it is really crucial for road warriors...
Thanks!

Revision history for this message
TJ (tj) wrote :

I've been running openvpn client over wireless LAN since 6.10 with no issues. You'll need to give precise details of the configuration of the network and openvpn.

Revision history for this message
Andy Rogers (andy-rogers) wrote :

Please provide details of your actual system setup, your configuration files etc.
This could be just a misconfiguration.

Changed in openvpn:
status: New → Incomplete
Revision history for this message
firebird (sysadmin-dk-compmath-deactivatedaccount) wrote :

sure, whatever you need!
Intrepid's network setup is an out of the box setup, i didn't change anything there, exept that i configured a static ip instead of a dynamic one for the wired connection.

Revision history for this message
firebird (sysadmin-dk-compmath-deactivatedaccount) wrote :

uh, one thing i missed; i added the keyword "float" to the config right below the line with the "remote" keyword, as an error on first connection attempt tells me to do so.

Revision history for this message
TJ (tj) wrote : Re: [Bug 347788] Re: OpenVPN client does not recognize WLAN connections

What does /var/log/daemon.log report when the connection is being
attempted?

Revision history for this message
Thierry Carrez (ttx) wrote :

From my understanding you are using :
- NetworkManager to handle your network connection
- OpenVPN service to establish VPN at boot

This combination won't work : the network won't be available until you log into Gnome, so the VPN cannot be established at boot. If you are using that combination, I'd recommend fallback to using either Networkmanager + network-manager-openvpn, or define your network in /etc/network/interfaces (disabling NM) and use the OpenVPN service to establish the connection at boot time.

Revision history for this message
TJ (tj) wrote :

If the wireless interface is configured as 'system-wide' in NetworkManager the host interface will be up without a log-in and openvpn will establish the tunnel as soon as the route appears.

If NetworkManager establishes the wireless connection after GDM log-in the openvpn connection establishes itself as soon as the route appears.

I don't have any openvpn connections defined via NetworkManager. I have the openvpn service defined in /etc/openvpn/connection.conf. /etc/rc2.d/S16openvpn runs at boot-time.

Revision history for this message
Thierry Carrez (ttx) wrote :

True, openvpn should retry until the connection is open. So it /should/ work :)

Revision history for this message
firebird (sysadmin-dk-compmath-deactivatedaccount) wrote :

ok, i am starting to understand, what you meant by "more information on the configuration":
i have defined the LAN connection during installation of intrepid, and of course i can see it in network-manager as eth0.
checkbox "system setting" is enabled there.

the vpn is not configured in network-manager as i am using pkcs12 (ie. *.p12) certificates which are currently not supported by network-manager.
the vpn is not being established automatically during system startup, but i have installed openvpngui, which is a very simple to use taskbar applet that uses the config files in /etc/openvpn and that allows to select between several different configs.
this implies that all routes should practically be there, as i of course gnome needs to be running in order to use openvpngui.

btw. the wireless connection is also not being started automatically during system startup, but i connect manually through the network-manager taskbar applet.
the reason for this is that i run from one institute to another and all of those of course have differen networks...

please see the attachment for information on the daemon.log

Revision history for this message
firebird (sysadmin-dk-compmath-deactivatedaccount) wrote :

err yes, as far as i can see with tail -f on /var/log/daemon.log nothing is being inserted there if i start the vpn via openvpngui, so heres another log from the openvpn output window.
i believe these two lines to be the interesting ones:

Wed Mar 25 10:17:01 2009 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Mar 25 10:17:01 2009 TLS Error: TLS handshake failed

Thierry Carrez (ttx)
Changed in openvpn (Ubuntu):
status: Incomplete → New
Chuck Short (zulcss)
Changed in openvpn (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
firebird (sysadmin-dk-compmath-deactivatedaccount) wrote :

Hi Chuck!

As I can see somebody still cares about this so I wanted to let you know that this woks now!
I have no idea what has been changed but I tried it once more the other day and it works now, so from my point of wiev this thread can be closed.
Your's, firebug

Chuck Short (zulcss)
Changed in openvpn (Ubuntu):
status: Triaged → Fix Released
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.