From 29cceb59a5b58d8c00a78022091f78838392cdce Mon Sep 17 00:00:00 2001 From: Patric Stout Date: Thu, 15 Jul 2021 19:43:01 +0200 Subject: Doc: explain in a bit more detail how we implemented STUN --- src/network/network_coordinator.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'src/network/network_coordinator.h') diff --git a/src/network/network_coordinator.h b/src/network/network_coordinator.h index 9dd4c9b39..f6859f859 100644 --- a/src/network/network_coordinator.h +++ b/src/network/network_coordinator.h @@ -16,6 +16,8 @@ /** * Game Coordinator communication. + * For more detail about what the Game Coordinator does, please see + * docs/game_coordinator.md. * * For servers: * - Server sends SERVER_REGISTER. @@ -34,7 +36,7 @@ * - Send the client a GC_CONNECT with the peer address. * - a) Client connects, client sends CLIENT_CONNECTED to Game Coordinator. * - b) Client connect fails, client sends CLIENT_CONNECT_FAILED to Game Coordinator. - * 2) STUN? (see https://en.wikipedia.org/wiki/STUN) + * 2) STUN? * - Game Coordinator sends GC_STUN_REQUEST to server/client (asking for both IPv4 and IPv6 STUN requests). * - Game Coordinator collects what combination works and sends GC_STUN_CONNECT to server/client. * - a) Server/client connect, client sends CLIENT_CONNECTED to Game Coordinator. -- cgit v1.2.3-54-g00ecf