Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41634 - [openvpn] systemd service should pull in networkd-online.target

Attached to Project: Arch Linux
Opened by Marius (65kid) - Wednesday, 20 August 2014, 12:14 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 20 August 2014, 14:41 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

openvpn@.service should add the following in the [Unit] section to make sure the network is up before it is started:

Wants=network-online.target
After=network-online.target

see also:

http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 20 August 2014, 14:41 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#40838 
Comment by Dave Reisner (falconindy) - Wednesday, 20 August 2014, 13:28 GMT
For some people, the definition of "online" isn't satisfied until after the VPN has been established.
Comment by Marius (65kid) - Wednesday, 20 August 2014, 13:40 GMT
I see your point, but I think it is far more common that the VPN can't be established in the first place if the network isn't up.

In my particular case I want to connect to an anonymous VPN provider but it sometimes fails to resolve the hostname on boot. Using network-online.target together with systemd-networkd-wait-online.service fixes this properly.

For people whose definition of "online" is "VPN is up" the current behaviour is broken as well and adding this wouldn't make it worse. They could still fix this themselves with a unit.d snippet.

Loading...