Ubuntu
openvpn package

OpenVPN client always runs

Bug #427701 reported by cprise
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Server papercuts
Invalid
Medium
Thierry Carrez
Ubuntu Server papercuts lucid-beta-1
openvpn (Ubuntu)
Expired
Wishlist
Unassigned

Bug Description

Binary package hint: openvpn

OpenVPN is being run at startup automatically, preventing desktop (client) users from easily running and stopping it as a client: the original OpenVPN instance is blocking.

NOTE: The (kubuntu 9.04 AMD64) systems this problem pertains to have had the knetworkmanager abomination removed in favor of wicd. :) Therefore, networkmanager-style handling of the vpn is not available and other means of starting the vpn link are being used.

I don't see the point in running OpenVPN at startup on the desktop distro. It causes VPN scripts and alternative front-ends to break, reporting that the port is already in use. On desktop/laptop systems, OpenVPN should not be run automatically as if it were a service. What results from the current behavior is that an OpenVPN client is run at startup and just sits there because the user hasn't yet established their Wifi link; when the user has a Wifi link and goes to initiate an OpenVPN connection, a "port already in use" error is generated and they do not get a safe connection.

PLEASE FIX.

Revision history for this message
Mathias Gug (mathiaz) wrote : Re: [Bug 427701] [NEW] OpenVPN client always runs

On Fri, Sep 11, 2009 at 05:09:12AM -0000, cprise wrote:
> Public bug reported:
>
> Binary package hint: openvpn
>
> OpenVPN is being run at startup automatically, preventing desktop
> (client) users from easily running and stopping it as a client: the
> original OpenVPN instance is blocking.
>

Could you try to set AUTOSTART="none" in /etc/default/openvpn? That
should disable starting any vpns by default on boot.

The default value of AUTOSTART is all, which means starting all
configure vpn services. It may make sense to change the default value to
none (since no vpn are configured by default on package installation).

 status triaged
 importance wishlist

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

Changed in openvpn (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Thierry Carrez (ttx)
Changed in server-papercuts:
importance: Undecided → Medium
status: New → Confirmed
Thierry Carrez (ttx)
Changed in server-papercuts:
milestone: none → lucid-beta-1
assignee: nobody → Thierry Carrez (ttx)
Revision history for this message
Thierry Carrez (ttx) wrote :

I verified that if you don't explicitly drop a configuration in /etc/openvpn, OpenVPN won't start anything. So the default is satisfying: if you have openvpn installed and don't do anything with /etc, nothing happens, nothing is started, nothing conflicts. If you add a configuration in /etc/openvpn, then it will be started at boot, unless you change the default behavior in /etc/default/openvpn.

I fail to see where openvpn behavior is breaking alternative front-ends, since they don't (shouldn't) touch /etc/openvpn. Could you explain that ?

Marking as invalid for papercut, since the bug is incomplete and solution is no longer obvious.

Changed in server-papercuts:
status: Confirmed → Invalid
Changed in openvpn (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openvpn (Ubuntu) because there has been no activity for 60 days.]

Changed in openvpn (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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