You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suppose anyone behind NAT met situation when your friends can't connect through steam to your lobby. Or directly to your server by IP.
Custom master server has static IP so theoretically it can function like STUN server. When a heartbeat packet received from server, master adds source ip:port to its list and sending this list to each client with getServersResponse. Why not send some kind of "heartbeat response" contains ip:port back to server? If admin has dynamic IP, even if behind different types of NAT admin will see that his server registered on master successfully. Using this IP client can connect to server for the first time.
The text was updated successfully, but these errors were encountered:
I suppose anyone behind NAT met situation when your friends can't connect through steam to your lobby. Or directly to your server by IP.
Custom master server has static IP so theoretically it can function like STUN server. When a heartbeat packet received from server, master adds source ip:port to its list and sending this list to each client with
getServersResponse
. Why not send some kind of "heartbeat response" contains ip:port back to server? If admin has dynamic IP, even if behind different types of NAT admin will see that his server registered on master successfully. Using this IP client can connect to server for the first time.The text was updated successfully, but these errors were encountered: