Open mickvandijke opened 1 month ago
cc @b-zee @joshuef @grumbach
I have searched the forums and Discord but can not find people experiencing the same problem. If this is a bug, it's likely a bug that needs fixed in libp2p
.
Depending on how many bump into this problem, it can cause problems. However, home nodes should function properly even without port forwarding by using relays.
Opened an issue on the libp2p repo for this: https://github.com/libp2p/rust-libp2p/issues/5506
I have opened a PR to fix this in igd-next (which libp2p uses): https://github.com/dariusc93/rust-igd/pull/8
The issue was that I have multiple UPnP enabled devices on my network (like a Philips HUE bridge). When searching for a router/gateway to open the UPnP ports on, igd-next incorrectly assumed that the first UPnP enabled device would be the router (but for me, it happened to be my HUE bridge). Instead of trying other UPnP enabled devices to look for the router, the search would just fail if the first device is not the router/gateway.
I noticed that nodes weren't opening any ports on my router through UPnP. I checked with
miniupnpc
and in my router logs. UPnP is definitely supported and enabled on my ASUS consumer router (tested it with other apps and miniupnpc).So I checked the node logs to see what is going on:
It looks like the issue stemmed from
libp2p
. To test it, I ran the libp2p upnp example and got this error:Again, I saw that no ports were opened.
@b-zee then asked me to test the
igd_next
example, which did work:I'm afraid that lots of other users are running into the same issue without them knowing. Perhaps this is the reason that some users report not receiving any node rewards?