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'm running a pod that uses discv5 for discovery on UDP port 9200. It communicates with a bootnode on the same port to kickstart peer discovery.
The problem: the packet payload advertises the node's IP and port 9200, but SNAT rewrites the source port on the way out. The bootnode sees a mismatch between the advertised port and the actual source port of the packet, and discards the peer.
Is there a way to prevent SNAT/masquerade from rewriting the source port on these UDP packets?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm running a pod that uses discv5 for discovery on UDP port 9200. It communicates with a bootnode on the same port to kickstart peer discovery.
The problem: the packet payload advertises the node's IP and port 9200, but SNAT rewrites the source port on the way out. The bootnode sees a mismatch between the advertised port and the actual source port of the packet, and discards the peer.
Is there a way to prevent SNAT/masquerade from rewriting the source port on these UDP packets?
All reactions