I can't ping but I can resolve names. Any suggestions? I tried the usual, ICMP and firewall. I can ping the netmaker-1 node, and I can ping zelf. But I can't ping any other node. I have done docker down/up and found no errors in the logs. I have deployed nodes inside and outside my network. I am testing on a mac and three proxmox server (debian). I get this on the three nodes

bash
root@pve3:~# ip route
default via 10.1.1.1 dev vmbr0 proto kernel onlink
10.1.1.0/24 dev vmbr0 proto kernel scope link src 10.1.1.63
10.58.65.0/24 dev nm-office-vpn scope link
10.58.65.1 dev nm-office-vpn scope link
10.58.65.2 dev nm-office-vpn scope link
10.58.65.4 dev nm-office-vpn scope link
10.58.65.254 dev nm-office-vpn scope link
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0

bash
root@pve2:~# ip route
default via 10.1.1.1 dev vmbr0 proto kernel onlink
10.1.1.0/24 dev vmbr0 proto kernel scope link src 10.1.1.62
10.58.65.0/24 dev nm-office-vpn scope link
10.58.65.2 dev nm-office-vpn scope link
10.58.65.3 dev nm-office-vpn scope link
10.58.65.4 dev nm-office-vpn scope link
10.58.65.254 dev nm-office-vpn scope link
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0

bash
root@pve1:~# ip route
default via 10.1.1.1 dev vmbr0 proto kernel onlink
10.1.1.0/24 dev vmbr0 proto kernel scope link src 10.1.1.61
10.58.65.0/24 dev nm-office-vpn scope link
10.58.65.1 dev nm-office-vpn scope link
10.58.65.3 dev nm-office-vpn scope link
10.58.65.4 dev nm-office-vpn scope link
10.58.65.254 dev nm-office-vpn scope link
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0
xxx via 10.1.1.1 dev vmbr0

Do the nodes have handskakes?

Hi, yes they do, sorry. Here is the output:

bash
root@pve1:~# wg show
interface: nm-office-vpn
  public key: xxx
  private key: (hidden)
  listening port: 53408

peer: xxx
  endpoint: 10.1.1.100:51821
  allowed ips: 10.58.65.4/32
  latest handshake: 25 seconds ago
  transfer: 69.25 KiB received, 765.80 KiB sent
  persistent keepalive: every 20 seconds

peer: xxx
  endpoint: xxx:51821
  allowed ips: 10.58.65.254/32
  latest handshake: 1 minute, 57 seconds ago
  transfer: 40.60 KiB received, 164.29 KiB sent
  persistent keepalive: every 20 seconds

peer: xxx
  endpoint: 10.1.1.63:42484
  allowed ips: 10.58.65.3/32
  latest handshake: 15 hours, 13 minutes, 50 seconds ago
  transfer: 936 B received, 1.31 MiB sent
  persistent keepalive: every 20 seconds

peer: xxx
  endpoint: 10.1.1.62:55442
  allowed ips: 10.58.65.1/32
  latest handshake: 15 hours, 13 minutes, 53 seconds ago
  transfer: 568 B received, 1.32 MiB sent
  persistent keepalive: every 20 seconds

peer: xxx
  endpoint: xxx:44305
  allowed ips: 10.58.65.5/32
  transfer: 0 B received, 1.30 MiB sent
  persistent keepalive: every 20 seconds

the last peer does not have a handshake and the other two with handshakes over 15 hours ago are also suspect. Usual reason for failure to obtain handshakes is either incorrect publickey or incorrect endpoint --- either the ip or the port

I am really not sure what I am missing here. I have torn it all down and set it up again 3 times, using the quick start script and the standard install. I admit being new to wireguard, but I am just not seeing anything helpful to dig into to troubleshoot. The handshake initially takes place and then no more. It really seems to be happening in my own network. I have turned on UPNP. I have the same network at home as I do for my clients, so I kind of am worried it won't be stable. For comparison, when using slackHQ Nebula I have handshakes and pings galore, no interruptions ever. So I feel like it's somethign I am doing wrong.

@bright-hairdresser-26203 did you ever figure this out? my buddy and I are having similar issues (except we haven't been able to handshake at all except between two of his devices only on his network)