Hi there, I'm new to netmaker, so I'm not sure if ...
# client
s
Hi there, I'm new to netmaker, so I'm not sure if I'm just missing something. I have the netmaker server set up on a remote server and that seems to be fine. I also have netclient set up on a different remote server. And then I have netclient set up on a couple "local" machines (remote from both of the other servers). My local servers can talk to the remote client without any issues, and the remote clients can talk to my local clients. But the problem is the two local machines can't talk to each other for some reason. Can someone point me at what to look at?
The local machines are on the same subnet, but
wg show
shows my public ip as the endpoint for both of them. I'm wondering if that's the problem
b
It is. The endpoint of a node on the same lan should be it's lan address
s
How's that logic work? I checked /etc/netclient/config/netconfig-* and it has the correct local ip under node.localaddress
b
It is a bit complicated, especially if there are multiple interfaces and IP addresses on the local machine.
s
Does it use the WAN ip by any chance? (the one seen by the netmaker server) I just noticed sometimes wg show actually does have the local ip, but then it'll change back to my wan ip. But I have two WAN ips, so both servers are in the same lan but may look like they're coming from different public ips
I think I got it partially working.... I set my router to only use a single WAN gateway for now, and then I had to manually update the node endpoint ip in the netmaker ui. Once they all had the same public ip,
wg show
showed the correct endpoint ip for the local machines.
After that though, I had to disable udp hole punching so that I could allow a single port through the firewalls. I'm not sure how to allow the traffic otherwise when it uses random ports?
2 Views