Thanks for the info. I’m not sure if the issue you describe is what I am seeing, because I am trying to access a server using the IP address, not domain name. However, I do understand that it may be related.
I can fix the connection issue by adding an entry to the routing table for my private cloud server. This guarantees that traffic to the server bypasses the VPN on the GL-AR750S.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default * 184.108.40.206 U 0 0 0 tun0
default 192.168.20.1 0.0.0.0 UG 10 0 0 eth0.2
10.15.0.0 * 255.255.0.0 U 0 0 0 tun0
YYY.YYY.YYY.YYY 192.168.20.1 255.255.255.255 UGH 0 0 0 eth0.2
220.127.116.11 * 18.104.22.168 U 0 0 0 tun0
192.168.8.0 * 255.255.255.0 U 0 0 0 br-lan
192.168.20.0 * 255.255.255.0 U 10 0 0 eth0.2
XXX.XXX.XXX.XXX 192.168.20.1 255.255.255.255 U 0 0 0 eth0.2
The routing table shows that the default gateway for all traffic is through the VPN tunnel. Enabling the VPN Policy does not modify the routing table. Please note that the IP address of the Mullvad OpenVPN server is shown as YYY.YYY.YYY.YYY.
After I add a route entry for my private cloud server IP address (shown as XXX.XXX.XXX.XXX), my connection to the server is stable and routed correctly. All other traffic is correctly routed through Mullvad OpenVPN on the GL-AR750S.
This is only a temporary fix and needs to be configured after each power-up. If anyone has any more suggestions, I’m willing to give them a try.