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
This is a problem in the original upnpbeacon too. (and it's not a big deal, but reporting for completeness after testing this one too)
If you have two ip addresses on an interface, u2pnpd will only listen on one of them. I would think that without specifying an interface or an IP, it should listen to 0.0.0.0. (This may be a problem in libupnp, but it manifests in the apps themselves)
The text was updated successfully, but these errors were encountered:
When I understand it correctly, then libupnp does not provide the required internal infrastructure to distinguish between various addresses of the same type (i.e. multiple IPv4 addresses), it only differentiates between IPv4 vs IPv6.
I'll leave this issue open as a reminder, and when I find time I consider to have a deeper look at libupnp - but to be honest, it will be only low priority. But thanks for reporting so far, I did not yet noticed this as my requirements and tests were only "simple" setups and mostly IPv4 only.
Totally understand :) It's just something I'd run across in upnpbeacon, and was hoping your "improved" version would just magically fix some things for me. They're not a big deal, it just took me a while to figure out what was wrong the first time I had two IPs on an interface :)
This is a problem in the original upnpbeacon too. (and it's not a big deal, but reporting for completeness after testing this one too)
If you have two ip addresses on an interface, u2pnpd will only listen on one of them. I would think that without specifying an interface or an IP, it should listen to 0.0.0.0. (This may be a problem in libupnp, but it manifests in the apps themselves)
The text was updated successfully, but these errors were encountered: