In conjunction with the controller version 5.9.31 I have been playing around with wireguard.
While I can get it to connect and pass some data it is somewhat intermittant, if I run a ping test to a mobile android device the pings are only about 25% successful. (the mobile is off WiFi on the cellular network) so connected via WAN.
From the mobile device I want to push all traffic down the tunnel and then route through the home internet connection, so 0.0.0.0/0 configured on the client, again it works sometimes.
From the client I cannot connect to any device in my internal networks, despite having the subnets they are in as allowed.
I'm a network engineer so familar with what I am doing and how things should be to route. I have no overlapping networks and everything reads as if it is configured correctly.
The routing table shows none of the networks configured for Wireguard which seems a little odd, but Wireguard I am not familiar with.
Is this still in its infancy wth TP Link with some of the usual beta test it in the wild bugs, has anyone else managed to get it to work properly and reliably.
I would expect if ACLs needed to be configured I would see an interface in the menus, I tried creating an IP group for the the wireguard subnet and opening that up as much as possible but made no difference.
Also need an export the settings function like OpenVPN to make setting the client up easier rather than copy pasting keys into files and sending them back and forth.
OpenVPN which I have setup works a treat.