I've got an issue with a client. I've joined the n...
# client
b
I've got an issue with a client. I've joined the network and everything shows healthy in the UI, but I'm unable to ping or SSH to any nodes and other nodes can't ping or SSH to it
b
Have you tried doing a pull in the node?
b
let me try now
Seems to work fine
b
Upp hole punching on for the network and node behind NAT?
b
UDP hole punching is on and yes
b
Sometimes it takes a little while for the wireguard interface to become operational in that scenario
Not sure exactly why
b
client is running on host machine (same as the netmaker compose stack) and another client is off-site in another state. I can ping / ssh into the remote machine from the netmaker container, but even the host machine is unable to ping the netmaker node's IP
but the host client (the problematic one) is able to ping it's own netmaker IP
b
Are handshakes established with other node (wg show)
any Rx bytes in peer section
b
No: transfer: 0 B received, 8.67 KiB sent
It also doesn't list the server node as a peer
Only the remote pi
remote pi lists both with wg show
b
the host node and netmaker server are going to have the same public IP which may be causing issues with overlapping routes
What is listen port on the node on the host
b
Ah didn't think about that
b
It has to be outside the range of 51821-51830 as that range is mapped to netmaker container
b
Ah
It doesn't look like I can edit the node port in the UI
b
Turn off UDP hole punching for that node
b
I don't see a switch for hole punching in the node UI
b
Is static toggle beside the listenport
b
Dynamic Port?
b
Yes
b
Ah got it
Had to save for it to become editable
That did it. Thanks!
b
3 Views