clarify documentation for outgoing_interfaces

This commit is contained in:
Arvid Norberg 2020-04-01 15:12:30 +02:00 committed by Arvid Norberg
parent 93aa1956a4
commit ef7362f140
1 changed files with 18 additions and 11 deletions

View File

@ -192,17 +192,24 @@ namespace aux {
// used instead // used instead
handshake_client_version, handshake_client_version,
// sets the network interface this session will use when it opens // This controls which IP address outgoing TCP connections are bound
// outgoing connections. An empty string binds outgoing connections to // to, in addition to controlling whether such connections are also
// INADDR_ANY and port 0 (i.e. let the OS decide). The parameter must // bound to a specific network interface/adapter (*bind-to-device*).
// be a string containing one or more, comma separated, adapter names. // This string is a comma-separated list of IP addresses and
// Adapter names on Unix systems are of the form "eth0", "eth1", // interface names. An empty string will not bind TCP sockets to a
// "tun0", etc. When specifying multiple interfaces, they will be // device, and let the network stack assign the local address. A
// assigned in round-robin order. This may be useful for clients that // list of names will be used to bind outgoing TCP sockets in a
// are multi-homed. Binding an outgoing connection to a local IP does // round-robin fashion. An IP address will simply be used to `bind()`
// not necessarily make the connection via the associated NIC/Adapter. // the socket. An interface name will attempt to bind the socket to
// Setting this to an empty string will disable binding of outgoing // that interface. If that fails, or is unsupported, one of the IP
// connections. // addresses configured for that interface is used to `bind()` the
// socket to. If the interface or adapter doesn't exist, the
// outgoing connection will failed with an error message suggesting
// the device cannot be found. Adapter names on Unix systems are of
// the form "eth0", "eth1", "tun0", etc. This may be useful for
// clients that are multi-homed. Binding an outgoing connection to a
// local IP does not necessarily make the connection via the
// associated NIC/Adapter.
outgoing_interfaces, outgoing_interfaces,
// a comma-separated list of (IP or device name, port) pairs. These are // a comma-separated list of (IP or device name, port) pairs. These are