Change Details

For people with routers not supporting NAT loopback, it is not possible to join a lobby game from someone hosting from the same network (e.g. another computer, the same computer). This is annoying because it prevents: - having a dedicated server at home - playing with your friends at home via the lobby (which can be easier than via regular MP). Unfortunately, there is no trivial solution to 2 problems: - Finding the local IP - I'm using https://stackoverflow.com/a/59025254 but it needs another look - deciding how to switch local/remote. My approach is to do an external IP query first, then an internal IP query if the first reveals that the IPs are the same. This will be a little slower, but that should be OK in general. We _could_ just return both in one go. TODO: - no idea if this compiles on windows/*nix/freebsd/etc.

For people with routers not supporting NAT loopback, it is not possible to join a lobby game from someone hosting from the same network (e.g. another computer, the same computer). This is annoying because it prevents: - having a dedicated server at home - playing with your friends at home via the lobby (which can be easier than via regular MP). The solution is to open a socket and find the local IP. My solution is based on https://stackoverflow.com/a/59025254 which should work even without proper internet. The client will query its public IP, match against the server, and if they are the same, assume they're on the same network & try to use the local IP instead.

For people with routers not supporting NAT loopback, it is not possible to join a lobby game from someone hosting from the same network (e.g. another computer, the same computer). This is annoying because it prevents: - having a dedicated server at home - playing with your friends at home via the lobby (which can be easier than via regular MP). Unfortunately, there is no trivial solution to 2 problems: - Finding the local IP - I'm using https://stackoverflow.com/a/59025254 but it needs another look - deciding how to switch local/remote. My approach is to do an external IP query first, then an internal IP query if the first reveals that the IPs are the same. This will be a little slower,The solution is to open a socket and find the local IP. but that should be OK in general. We _cMy solution is based on https://stackoverflow.com/a/59025254 which should_ just return both in one go work even without proper internet. TODO: - no idea if this compiles on windows/*nix/freebsd/etche client will query its public IP, match against the server, and if they are the same, assume they're on the same network & try to use the local IP instead.