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
The initial handshake to exchange information works nicely, but after getting the public IP and ports, when the peers try to fire a packet to one another the packet was seemingly going nowhere.
I completely missed the fact that on giving the packet a new address(the remote peer address rather than the relay address) a new binding was created in the NAT even when sending the packet from the same port. So the problem was both the peers were sending packets to ports which were being used for the relay connection and thus due to symmetric NAT and not matching the remote address in the connection the packets were essentially getting discarded on the side of the receiver.
The text was updated successfully, but these errors were encountered:
orangeseeds
changed the title
Find solution to the problem of port assignment by Symmetic NAT
Implement NAT Traversal for symmetic NAT
Feb 25, 2024
The initial handshake to exchange information works nicely, but after getting the public IP and ports, when the peers try to fire a packet to one another the packet was seemingly going nowhere.
I completely missed the fact that on giving the packet a new address(the remote peer address rather than the relay address) a new binding was created in the NAT even when sending the packet from the same port. So the problem was both the peers were sending packets to ports which were being used for the relay connection and thus due to symmetric NAT and not matching the remote address in the connection the packets were essentially getting discarded on the side of the receiver.
The text was updated successfully, but these errors were encountered: