-
Notifications
You must be signed in to change notification settings - Fork 60
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
should bind on ipv4 and ipv6 per default #54
Comments
This sounds a lot like a firewall issue. What do you mean "ports are opened"? Can you try something like the following: On hostA: On hostB: This should allow you to type stuff in one terminal and see it appear in the second. If that doesn't work, then you have a network issue and something is filtering the packets. You should also try the same for port 7946. |
I realized that nc over IPv4 works perfectly, so I tried connecting wesher through IPv4 and it connects and I can ping the two hosts using the in-tunnel IPv4 address. Here's what I did: On Host A: On Host B: They connect. (Not sure what happened when I posted my OP stating it doesn't work over IPv4) However connecting through IPv6 still yielded the same errors as above. I double checked the firewalls on both hosts and the have been set up to allow connections on ports 7946 and 51820. |
I have to specifically bind wesher on Host A to use IPv6 address in order to let Host B to connect via IPv6. |
Indeed, the automatic binding isn't picking up ipv6. Will have to look into it. |
I have having a hard time joining the mesh network started by the designated VPS.
The error message is always either 'connection refused', or 'i/o timeout'.
I was connecting both through IPv4 and IPv6 and got the same results.
Ports are opened.
The text was updated successfully, but these errors were encountered: