Skip to content

Comments

fix: don't use invalid port 0 when NATMap fails#3058

Closed
wlynxg wants to merge 1 commit intolibp2p:masterfrom
wlynxg:natmap_error
Closed

fix: don't use invalid port 0 when NATMap fails#3058
wlynxg wants to merge 1 commit intolibp2p:masterfrom
wlynxg:natmap_error

Conversation

@wlynxg
Copy link
Contributor

@wlynxg wlynxg commented Nov 21, 2024

fix: #3057

Copy link
Member

@sukunrt sukunrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @wlynxg

@p-shahi
Copy link
Member

p-shahi commented Dec 2, 2024

@wlynxg thanks for the contribution - Would you like to address Sukun's feedback?

@wlynxg
Copy link
Contributor Author

wlynxg commented Dec 3, 2024

@wlynxg thanks for the contribution - Would you like to address Sukun's feedback?

I will refer to Sukun's feedback and re-edit the code later.

@sukunrt
Copy link
Member

sukunrt commented Dec 8, 2024

Apologies for the confusion here. This specific method's code is too confusing. I think your original approach of erroring when port is 0 was correct.

closing in favour of: #3094
rest is handled by: #3075

@sukunrt sukunrt closed this Dec 8, 2024
@wlynxg wlynxg deleted the natmap_error branch January 21, 2025 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NATMap mapping failed, resulting in an observed address error

3 participants