@test01 Just edit your VPN settings to change the .1 to a .2 Then from the controller, go to Insights->Routing Table, and screen grab that

@test01 Ok above is good...looks the routing hiccup is in one or both of the routers. Can you make the Hail Mary changes and then send the Controller's routing table?

@test01 Can you also provide the controller's Insights->Routing Table info (public IP partially anonymized (ie leave first and last digit visible only)) Since it seems your routers are .2 and not the...

@test01 The OSX equivalent of "route print" is "netstat -rnf inet"

And you tried this right? https://www.tp-link.com/en/support/faq/3114/

Ok, can you do three things and provide output? 1. ipconfig /all (delete any public IP info) 2. route print (delete any public IP info) 3. tracert 172.22.2.2