-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use localPort
option during TCP connect
#2620
Labels
kind/enhancement
A net-new feature or improvement to an existing feature
Comments
achingbrain
added
need/triage
Needs initial labeling and prioritization
kind/enhancement
A net-new feature or improvement to an existing feature
and removed
need/triage
Needs initial labeling and prioritization
labels
Jul 16, 2024
I think for this to work we need to be able to open ports with Other reading: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For autoNAT to work correctly, we should use the
localPort
option in socket.connect to ensure we use a predictable port. Otherwise we end up using ephemeral ports and each autoNAT interaction tries to confirm a different port number.The text was updated successfully, but these errors were encountered: