[arch-general] R: openvpn-client@ takes long time to start
Da: Giancarlo Razzolini Inviato: Venerdì, 14 Agosto, 2020 13:29 A: General Discussion about Arch Linux Cc: Riccardo Paolo Bestetti Oggetto: Re: [arch-general] openvpn-client@ takes long time to start Em agosto 14, 2020 3:58 Riccardo Paolo Bestetti via arch-general escreveu:
After a reboot, the first openvpn-client@ instance I try to start takes almost exactly two minutes to start. The instances before that one start just fine in a few seconds.
Guess you meant: "The instances *after* ..."
Yes I did. :)
When that happens, I can see from journalctl that the client actually starts in the first few seconds after the systemctl command. But then, the command doesn't terminate for two more minutes (with no further journal entries).
Openvpn has quite good logging capabilities that you can put to use here.
The output from OpenVPN indicates that the client is started within the first few seconds from when I give the `systemctl start openvpn-client@whatever` command (see previous email). The tun interface is created, opened, the routes are received and added to the routing table. All the usual stuff. Of course, I can also reach remote hosts through the VPN after that. The exact same thing (& output) happens if I try to start OpenVPN manually from the command line. Minus, of course, the two-minutes wait before the command returns.
Has anyone seen this before? What could it be?
So, get a network manager that can properly trigger network-online.target. Or, if your network manager is triggering it, then it means your network is not quite ready when it does.
See above. I also forgot to specify it also happens when the system has been up for hours. It really can't be that the network is not ready. I don't think there's anything much that could be disturbing it. I'm using systemd-networkd for everything + iwd for wireless. Riccardo
Regards, Giancarlo Razzolini
Em agosto 14, 2020 9:57 Riccardo Paolo Bestetti escreveu:
The output from OpenVPN indicates that the client is started within the first few seconds from when I give the `systemctl start openvpn-client@whatever` command (see previous email). The tun interface is created, opened, the routes are received and added to the routing table. All the usual stuff. Of course, I can also reach remote hosts through the VPN after that.
The exact same thing (& output) happens if I try to start OpenVPN manually from the command line. Minus, of course, the two-minutes wait before the command returns.
Again, use the openvpn log capabilities. I'd recommend a verbose of at least 3, for starters.
I also forgot to specify it also happens when the system has been up for hours. It really can't be that the network is not ready.
Are you using --daemon on your openvpn config file?
I don't think there's anything much that could be disturbing it. I'm using systemd-networkd for everything + iwd for wireless.
Well, you can paste your configuration (minus keys and user/auth). Regards, Giancarlo Razzolini
participants (2)
-
Giancarlo Razzolini
-
Riccardo Paolo Bestetti