Apparently, this is new:Once I changed this to 'false' in and move client.conf to /etc/openvpn
it now auto-starts on boot and also withand yes, it was my own stupidity.
I had this working under Jessie and decided I'd better upgrade to the lastest version of everything.
And I have 'up' and 'down' scripts in root, which didn't seem to bother Jessie, but Trixie doesn't let OpenVPN service access /root by default
Still, questions remain:
1. why does openvpn-client@.service force '--nobind' ?
2. even with 'local' removed from client.conf and 'ProtectSystem=false' in openvpn-client@.service it still won't find and load client.conf
Just odd.
Working now
But just odd
Code:
ProtectSystem=trueCode:
/lib/systemd/system/openvpn.serviceit now auto-starts on boot and also with
Code:
sudo service openvpn stopsudo service openvpn startI had this working under Jessie and decided I'd better upgrade to the lastest version of everything.
And I have 'up' and 'down' scripts in root, which didn't seem to bother Jessie, but Trixie doesn't let OpenVPN service access /root by default
Still, questions remain:
1. why does openvpn-client@.service force '--nobind' ?
2. even with 'local' removed from client.conf and 'ProtectSystem=false' in openvpn-client@.service it still won't find and load client.conf
Just odd.
Working now
But just odd
Statistics: Posted by Prof. R. Myrkr — Mon Dec 08, 2025 12:46 am