diff options
| author | GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> | 2022-08-05 11:44:59 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-05 11:44:59 +0200 |
| commit | f5cc52b21fccb17fe5321fb8322648baaae7b6e2 (patch) | |
| tree | d562d54881086db0be640f0b20681c4182b1ab64 | |
| parent | e89e43ee2a994374969bec68d9b57fe90c0872ad (diff) | |
| download | NorthstarWiki-f5cc52b21fccb17fe5321fb8322648baaae7b6e2.tar.gz NorthstarWiki-f5cc52b21fccb17fe5321fb8322648baaae7b6e2.zip | |
Add note about NAT loopback
| -rw-r--r-- | docs/hosting-a-server-with-northstar/troubleshooting.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/hosting-a-server-with-northstar/troubleshooting.md b/docs/hosting-a-server-with-northstar/troubleshooting.md index 37a37f6..d258392 100644 --- a/docs/hosting-a-server-with-northstar/troubleshooting.md +++ b/docs/hosting-a-server-with-northstar/troubleshooting.md @@ -76,3 +76,14 @@ As two programs cannot listen to the same port and IP at the same time, changing **Server is using the wrong port** You can use `netstat -a -b` using CMD as admin to check which process listens on which port + +## Cannot join own dedicated server via serverbrowser but others can + +If you're hosting the dedicated server on the same network as the PC you're trying to join it from but are unabled to join it, the reason is likely that your router doesn't support [NAT loopback](https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback). + +The TL;DR is that basically when you connect via serverbrowser to your own dedicated gameserver located on the same network, the message goes to your router where it sees that the gameserver IP requested is the same as its IP address. A router that supports NAT loopback will still check forwarding rules, notice that it goes to your server and "turn the packet around" to your server. A router that doesn't support NAT loopback will simply drop the packet, meaning the request to join will never reach your gameserver. + +To work around this you can set `ns_auth_allow_insecure 1` on the gameserver in the `autoexec_ns_server.cfg`. This way you can directly connect to your server via `connect <local gameserver ip>:<port>` (e.g. `connect 192.168.123.456:37015`). + +Note that this still won't allow you to join your server via serverbrowser. You will always have to use the `connect` command to join it. Also, setting `ns_auth_allow_insecure 1` means that anyone that knows the server IP can join it without authenticating with masterserver, meaning that they can impersonate any player on your server. \ +To resolve this you will have to invest into a router that supports NAT loopback or host your gameserver outside your local network. |