What is a rationale for --no-bind in auto-services by Systemd?

Need help configuring your VPN? Just post here and you'll get that help.

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

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
brtb
OpenVpn Newbie
Posts: 1
Joined: Sun Apr 30, 2023 11:49 am

What is a rationale for --no-bind in auto-services by Systemd?

Post by brtb » Sun Apr 30, 2023 12:19 pm

Hi!

I'm looking at option "--no-bind" for an auto generated Systemd units to be started: (Debian 11 Bullseye):

Code: Select all

# cat /usr/lib/systemd/system/openvpn-client@.service | grep ExecStart
ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config %i.conf
Is there any rationale of no port binding at client side, if it's known beforehand the port number will NOT be occupied by a process?

To bind or not to bind is declared in configuration file on admin choice. But for auto-generated Systemd's units with clients it's enforced at start by direct option specification.

What a reason? Except a risk to catch a port collision issue.

Post Reply