OpenVPN fails to start on bullseye

This forum is for general conversation and user-user networking.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Post Reply
tomdechain
OpenVpn Newbie
Posts: 1
Joined: Thu Sep 28, 2023 7:27 pm

OpenVPN fails to start on bullseye

Post by tomdechain » Thu Sep 28, 2023 7:53 pm

Hello,

I recently moved from buster to bullseye and OpenVPN is the only installed package, as the RaspberryPi works as an OpenVPN Client.

There is no custom configuration so far.

The issue is if I use "enable" for starting the openvpn-Client@PiClient on startup, the status is "failed" and the system runs for minutes slowly.

I tried to use a custom waitfor.conf in the openvpn-client@service.d with the following service, targets and devices:

Code: Select all

[Unit]
After=network-online.target
Wants=network-online.target
#After=dhcpcd.service
#Wants=dhcpcd.service
#Requires=dhcpcd.service
#After=remote-fs.target
#After=nss-lookup.target
#Requires=network-online.target
#After=ssh.service
#Wants=ssh.service
#Requires=sys-subsystem-net-devices-eth0.device
#After=sys-subsystem-net-devices-eth0.device
After=systemd-time-wait-sync.service
Requires=systemd-time-wait-sync.service
The only solution which works in 7 out of 10 startups for starting the service successfully is by

Code: Select all

After=systemd-time-wait-sync.service
Requires=systemd-time-wait-sync.service
I am not that happy with this solution and I would like to identify the service, which blocks openvpn-client from a successful start.

Post Reply