Skip to content
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

Upnp port is not re-announced #2502

Open
master255 opened this issue Aug 18, 2023 · 5 comments
Open

Upnp port is not re-announced #2502

master255 opened this issue Aug 18, 2023 · 5 comments
Labels
effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue

Comments

@master255
Copy link

master255 commented Aug 18, 2023

@marten-seemann There is a serious problem with upnp port announcement.

Turn on the application (Libp2p application where there is upnp announcement). Upnp port is announced on the router. It is announced every minute.
Then turn off the internet connection in the router settings or pull the wire out of the router (emulate a real internet disconnection). Then turn on the Internet.
Check upnp ports. There are none. And, even after 5 minutes they do not appear.
This presents a serious problem. Because the stability of the internet connection is very bad all over the world (I checked).

@p-shahi p-shahi added the needs/triage Needs initial labeling and prioritization label Aug 18, 2023
@p-shahi
Copy link
Member

p-shahi commented Aug 18, 2023

@master255 Thanks for raising the issue but please do not tag Marten or individual maintainers directly. Tagging
individual maintainers is not necessary since everyone subscribed to the repo already get notifications for GitHub issues.
I've labeled this as needs/triage and someone on the team will investigate it (and we will discuss this in the next libp2p maintainers call) Thanks

@master255
Copy link
Author

Ok

@master255
Copy link
Author

As I understand the result of our discussion - we need to fix it.

@p-shahi p-shahi added this to the Best Effort Track milestone Aug 25, 2023
@marten-seemann
Copy link
Contributor

Discussed in the triage meeting. This will require debugging the UPnP code. It seems reasonable to periodically renew the UPnP mapping. Not sure if it's possible to trigger the renewal faster to be able to recover from this situation faster after a disconnect.

Fixing this issue won't be a priority for the libp2p stewards, but we'd be happy to review a PR.

@marten-seemann marten-seemann added help wanted Seeking public contribution on this issue good first issue Good issue for new contributors effort/hours Estimated to take one or several hours and removed needs/triage Needs initial labeling and prioritization labels Aug 25, 2023
@master255
Copy link
Author

I was able to fix it easily. Maybe it is necessary to do something else? #2583

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue
Projects
None yet
Development

No branches or pull requests

3 participants