@staples1347 

I think this only happens if you have 0.0.0.0/0 as destination. if you try this in controller mode, you have to readopt the router after every boot.

the rumors say that Policy route comes in Omada version 5.15/5.16 with associated router firmware

  @MR.S 

At the moment the Peer endpoint is set to the public ip of the remote wireguard server, Allowed Address is set to 10.17.0.0/18 , and I have Persistent Keepalive set to 14.  Also, I am running the router in standalone mode.  It's possible this is normal for wireguard as on full Linux servers, I normally also setup OSPF to go along with the vpn which keeps traffic flowing in both directions on a regular basis, but OSPF on this router doesn't seem to be showing the wireguard interface as an option.

  @staples1347 

I just setup a client to server Wireguard vpn on Linux and can confirm with persistent keepalive set to 14 seconds , the wireguard "client" sends keepalive packets every 14 seconds even if the interface isn't sending any packets so it looks like this isn't functioning on the TP-Link.  Note: To determine that the TP-Link wasn't sending keepalive packets, I ran tcpdump on the router that the TP-Link's wan interface was connected to in addition to running "wg show" on the wireguard server.