So I have two sites: my home network and my cloud VPSs. I have setup a FreeIPA domain that I would like to use for all my machines, local and remote. While I wait for Linode/Akamai to add their new VPC feature, I want to create Wireguard tunnels from each VPS to my home network with my UDMP as the router. I tried to set it up through the UI, however I can’t ping to/from the server wireguard interface when connected. So I tried to set it up with wg-quick but alas that isn’t working either. I have the firewall port for wireguard open with both Internet In and Internet Local. I’m not even trying to get LAN access yet because I can’t even ping over the tunnel. This has seriously frustrated me and I need to see if I’m just majorly fucking up or if I’m sane afterall and the UDMP just isn’t good for Wireguard. Server conf: [Interface] Address = 192.168.84.1/24 ListenPort = 51820 PrivateKey = [server private key] [Peer] PublicKey = [client public key] AllowedIps = 192.168.84.20/32 Client conf: [Interface] Address = 192.168.84.20/24 PrivateKey = [client private key] [Peer] PublicKey = [server public key] Endpoint = [server hostname]:51820 AllowedIPs = 192.168.84.1/32 I had PostUp and PostDown rules set, but they didn’t seem to make a difference. It seems they’re mostly for configuring routing with iptables. Can I please get a sanity check here? Edit: It was dns. It’s always dns. Apparently the UDM Pro doesn’t like IPv6 for Wireguard (and supposedly a lot) and the domain name I was using for my home network was double stack. I tested against it’s current IP address and when that worked I made a subdomain that was IPv4 only and it’s working great now.