-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 28 May 2021 07:58, Bo Berglund <bo.bergl...@gmail.com> wrote: > On Thu, 27 May 2021 23:26:00 +0000, tincantech via Openvpn-users > openvpn-users@lists.sourceforge.net wrote: > > > > I have looked at the /etc/default/openvpn file but there is nothing there > > > that > > > would cause the 3 instances to start running like this. > > > This file is where I usually specify which instances should run. > > > What has happened here? > > > From where were they started? > > > And how can I fix it such that only the instances I want running will run? > > > > Debian has a systemd unit file called openvpn.service, disable it. > > It starts all openvpn config files found in /etc/openvpn > > Openvpn ships with two specific systemd unit files: > > > > - openvpn-server@.service - For starting Openvpn servers > > - openvpn-client@.service - For starting Openvpn clients > > > > These two services only start a single instance as used by: > > > > - systemctl start openvpn-server@<your-server-file-name> (without .conf) > > - systemctl start openvpn-client@<your-client-file-name> (without .conf) > > > > The server service only starts openvpn config files in /etc/openvpn/server > > The client service only starts openvpn config files in /etc/openvpn/client > > https://github.com/OpenVPN/openvpn/blob/master/distro/systemd/README.systemd > > Should get you started. > > R > > Thanks! > I did not know this was happening, but wondered about the two empty folders > /etc/openvpn/server and /etc/openvpn/client that are created on installation > of > openvpn through apt... > > Does this mean that on Debian the /etc/default/openvpn file is not used at > all? > This is where I have specified which instances to run in the past. > > And does the install also provide for the creation of the routing IPTABLES > rules > I have otherwise had to make myself? > > My old notes started back in 2013 or so seems to have to be updated... > Debian switched to systemd but they choose to keep the old Sys-V init style of services around for compatibility. So you can still do: * service openvpn start And that is the script which uses /etc/default. As for iptables, I believe that is all up to you. Regards R -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsBzBAEBCAAGBQJgsMVrACEJEE+XnPZrkLidFiEECbw9RGejjXJ5xVVVT5ec 9muQuJ1RrAf9Hw4mz9RW7qf/WbPTKS6AoOXt1oreU4cHx24LVmMCrKdky3Bz UTWwlx9fRGsZSR9bwCKCU/5/Y3zw6gpqQtYfhFVAs195qH5CMTvf26subBeS KsnHRgoetRq9uU2M7duZotLrEUrBPuUqqKtHO6Nf66+xXJc/p2aCyeZcbNsV Q8ygSxYV0R6RkXm4kksPe9eOKG4suvEiFuCaFohwPdRiI4GSIrmBKTMx43qp 44oXJwG2kWL5rnDU6bMmOkv2RSE8syMq2oUXRqlMhEJuybs1t461WFl2A1bd 1Xiir1HvOkhen9gOGzWqQjrScUA/gvvGe0m/gU9sLy3j6jovpAVxHg== =hTyC -----END PGP SIGNATURE-----
publickey - tincantech@protonmail.com - 0x09BC3D44.asc
Description: application/pgp-keys
publickey - tincantech@protonmail.com - 0x09BC3D44.asc.sig
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users