FS#53447 - [openvpn] openvpn-client systemd unit --nobind option causes some configurations to fail to start

Attached to Project: Arch Linux
Opened by Dolf Andringa (dolfandringa) - Saturday, 25 March 2017, 05:27 GMT
Last edited by Christian Hesse (eworm) - Sunday, 23 April 2017, 20:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The openvpn-client systemd service specifies the --nobind option in the systemd unit file. In case a client config specifies the lport option, this causes an error when starting the systemd service:

"Options error: --lport and --nobind don't make sense when used together".

I believe this is a configuration option that should be left to the client config file and should not be specified in the openvpn-client systemd unit file.

I fixed this by removing the --nobind option from the ExecStart line in /usr/lib/systemd/system/openvpn-client@.service.

Additional info:
* at least openvpn 2.3.9 and up (including 4.2.1)
* openvpn config file that specifies the lport option


Steps to reproduce:
* Create an openvpn config with lport defined in /etc/openvpn/client/
* systemctl start openvpn-client@<your-config-file>
* openvpn throws an error and unit fails to start. Check logs with journalctl.
This task depends upon

Closed by  Christian Hesse (eworm)
Sunday, 23 April 2017, 20:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  We ship upstream files here. Please discuss with upstream if you think the behaviour is wrong.
Comment by Doug Newgard (Scimmia) - Monday, 27 March 2017, 17:40 GMT
This file comes from upstream, not from Arch. If you think it needs changed, you'll need to talk to them. As easy as it is to override things with drop-in configs, though, it's trivial to fix this locally.

Loading...