See NAT traversal for a high level description of how this works.
With p2p_broker running on my_p2p_broker.com register as
$ cargo run my_p2p_broker.com my_username
The following example uses the following IPs:
- broker: 22.214.171.124
- this_client: 126.96.36.199
- other_client: 188.8.131.52
other_client already registered. The flow is the same,
he just types
this_client registers and connects to
Client running on 0.0.0.0:63326 Registering as this_client with 184.108.40.206:63325... My public IP: 220.127.116.11 Listing users currently connected to 18.104.22.168:63325... other_client 22.214.171.124:63326 Type "listen<RET>" to listen for incoming connections, type "<username><RET>" to connect to it. other_client punching hole in own NAT to 126.96.36.199:63326 Listening for incoming messages... received MSG from 188.8.131.52:63326 hello this_client! > hello other_client!