From c3ed3b83246264b5b6f907e4b6f5fb85862db84b Mon Sep 17 00:00:00 2001 From: Peter L Jones Date: Wed, 7 Sep 2022 14:05:15 +0100 Subject: [PATCH] Use configured Directory Public IP for Client when hole-punching --- wiki/en/Directories.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/wiki/en/Directories.md b/wiki/en/Directories.md index 71e174436..7fa1131bb 100644 --- a/wiki/en/Directories.md +++ b/wiki/en/Directories.md @@ -23,8 +23,10 @@ When running a Server with the GUI, set the Custom Directory server address in t - If you want to control which Servers can register with your Directory, you can enable a whitelist with the `--listfilter` command line option in the format `ip address 1[;ip address 2]`. -- When running a Directory behind a NAT firewall on a private network, use the `--serverpublicip` option to specify the public IP address of the Server(s) being listed by your Directory if those Servers are on the same LAN / with the same public IP as the Directory. This is necessary to allow Clients on the public Internet to connect to them via NAT. Note that for the Servers using this option, you will still need proper port forwarding in your router/firewall. +- When running a Server behind a NAT firewall on a private network and registering with a Directory on the same network, run the Server using the `--serverpublicip` option to specify the public IP address. This is necessary to allow Clients on the public Internet to connect to the correct address. Note that for the Server(s) using this option, you will still need proper port forwarding in your router/firewall. -- If you are running your Server as a Directory and need to restart it for any reason (for example when rebooting the host), Servers connected to it will be disconnected until they re-register. This does not mean that Clients connected to those Servers will be disconnected, but does mean that new Clients will be not able to see Servers listed by your Directory until those Servers reconnect. To enable the list of registered Servers to persist between restarts, use the `--directoryfile` option to specify the location and name of a file that the Directory can read and write to. +- When running a Client behind a NAT firewall on a private network with a Directory on the same network, the Directory itself needs to be run using the `--serverpublicip` option to specify the public IP address, so that any Servers on the public Internet registering with the Directory that require the "hole punch" can be accessed by the Client(s). (This is because otherwise the Directory would provide the local network address of the Client to the Server and the "hole punch" would fail.) + +- If you need to restart your Directory for any reason (for example when rebooting the host), Servers connected to it will be disconnected until they re-register. This does not mean that Clients connected to those Servers will be disconnected, but does mean that new Clients will be not able to see Servers listed by your Directory until those Servers reconnect. To enable the list of registered Servers to persist between restarts, use the `--directoryfile` option to specify the location and name of a file that the Directory can read and write to. - Up to 150 Servers can then register with a Directory.