@AmazingMiki 

Hi,

If some services on 192.168.0.X (like vnc viewer) can be accessed, while some others (like ping) cannot, then it could be a firewall issue. (the firewall of the client machine 192.168.0.X)

I am not so familar with Linux, but for example the Windows Firewall has separate rules for local connections and remote connections. A client machine connected via the VPN connection will appear as a remote client.

"How can I configure openvpn to show me as yet another "local" device with 192.168.Y.Z subnet ip instead of a forein ip of 10.A.B.C which I have after openvpn connect?"

OpenVPN itself can be configured as a TUN or a TAP device. If configured as TAP device the VPN client would be in the same subnet as the VPN server.

However, TUN is the default for OpenVPN and TP-Link's router configuration GUI doesn't provide a way to configure it as TAP.

I HAVE been trying to save the subnet which was originall 10.8.0.0 to something more similar to the DHCP subnet of my LAN,

however, when I click save I just get some error message "(x) Operation failed."

when the subnet directly overlap with the DHCP subnet (192.168.0.0 instead of 192.168.1.0) is says that it can not overlap with the local DHCP subnet :(

  @AmazingMiki 

Yes, OpenVPN in "TUN" mode necessitates the subnet of the LAN and the subnet of the VPN to be different, otherwise it would screw up the network. So, the AX6000 is just preventing you from configuring something that wouldn't work anyway.