-
Notifications
You must be signed in to change notification settings - Fork 938
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
hole punching fails #46
Comments
Are 192.168.111.2 and 192.168.111.4 on the same local network? It seems surprising that the local packets are also failing, if so. IE:
which appears to show handshake attempts to |
yes, 192.168.122.1 is interface nodes 192.168.111.2 and 192.168.111.4 are on different routers, but has same ip segment |
Not out to necro this issue too much, but I also tried to set this up with a public lighthouse and a single node behind NAT tonight. I was unable to ping the lighthouse until I opened a node firewall port for 4242, even with reverse punching enabled. Wasn’t able to determine exactly why, but just wanted to mention it |
I seem to be seeing a similar issue. One lighthouse in digital ocean, and a node behind NAT at home. ping seems to be sent to lighthouse, inbound/outbound ACL set to all tcp/udp, yet ping blackhole'd. |
one lighthouse ip : 192.168.111.1
two local nodes are behind a difficult nat, ip : 192.168.111.2 and 192.168.111.4
two local nodes can not connect each other
here is node 192.168.111.2 logs
The text was updated successfully, but these errors were encountered: