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
[Bug]: multiple nodes (mesh clients) behind a single firewall/router cannot reach each other #2804
Comments
Have you set node A and node B as static hosts? |
No. The addresses for the nodes are being assigned sequentially by the netmaker server akin to dhcp |
We installed the mesh network overlay from defined/nebula and that doesn't appear to have this issue for hosts behind the same openwrt nat. I am puzzled that this is even an issue because it is the simplest candidate pair to discover when both hosts are behind the same nat |
Looks like there are others reporting similar issues. I certainly am not using static hosts. Are there assumptions being made about hairpining from the parent router that these two nodes are behind ? https://www.reddit.com/r/netmaker/comments/16wimqs/peer_to_peer_latency/ |
@abhishek9686 in the first case, wg show has the local ip Does that give you any ideas of how to fix the issue? Just as another data point, nebula/defined don't have this issue even when double natted. looking forward to hearing your insights in this matter |
those two nodes behind a double NAT, are they in the same local network? |
Yes on the same local network that is double natted |
if there are on local network, endpoint detection on netclient will set the endpoint to their local address, first it will check if it is able ping the other peer over the local address. |
@abhishek9686 |
Contact Details
What happened?
From the Troubleshooting FAQ
I tried setting a overlay mesh network of 2 nodes behind the a single firewall/router
10.20.30.1 is the netmaker server
10.20.30.2 is nodeA
10.20.30.3 is nodeB
nodeA can ping server
nodeB can ping server
nodeA cannot ping nodeB when using the netmaker interface even though they are on the same lan (and there is no peer isolation in play)
Version
v0.22.0
What OS are you using?
Linux
Relevant log output
We reproduced this issue in multiple instances and so cannot fault a specific openwrt router
Contributing guidelines
The text was updated successfully, but these errors were encountered: