-
Notifications
You must be signed in to change notification settings - Fork 158
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
Basic IPv6 support #800
Comments
My router doesn't allow me to redirect ports above 16383 for some reason, but it does give me an IPv6 address (presumably a static one). UPnP seems to fail :
I can't see my node on explorer.nkn.org, even after sync is done, so I assume NAT did not work indeed. IPv6 support should make all this irrelevant, no? |
@grondilu ipv6 is not quite relevant to the problem you encountered, you still have to open port automatically or manually. Have you searched how to set up port forwarding manually on your router? If it works you don't need to use UPnP |
I suppose. Though I thought with my own public IPv6 address I would have control other all the ports, which I don't with the IPv4 address for the reason below. I looked it up and apparently my ISP shares IP addresses between groups of 4 customers. So I can only redirect ports from 0 to 16383. Apprently I could ask a static IP with a "full stack" (https://forum.universfreebox.com/viewtopic.php?t=63369) but when I try they give me enough warnings to dissuade me. I'm confused as to why UPnP does not work. Is it because of this port limitation? Other P2P apps seem to work fine, and even the nkn client can still connect to other clients. I suppose I can get outbound connections but no inbound ones or something. |
I'm not quite sure. If the router is provided by your ISP then it could be, otherwise I guess it's more like a compatibility issue. We use a 3rd party library for UPnP setup, and you are definitely not the first person who encountered this problem. But even if UPnP works on your router, your ISP will still intercept the inbound connections before they reach your routers so it still won't work.
Exactly, that's one of the advantages of nkn client: it only uses outbound connections. |
Make sure NKN can run normally in a network where all nodes support ipv6, or ipv4+ipv6. This will ensure lowest level ipv6 compatibility.
Issue-Type (put a
x
sign in the square brackets)The text was updated successfully, but these errors were encountered: