Solved How to configure VPN Director with VPN for external IPs and LAN for internal IPs?

[ssh]

I am having trouble configuring VPN Director so that anyone on the LAN can connect to the router admin page https://www.asusrouter.com:8443/ and other internal IPs, while connections to the Internet would use a WG client. What keeps happening is that I eventually lose access to the router admin page and need to factory reset the router.

Enable	Description	Local IP	Remote IP	Iface
Y	LAN to Class C bypass VPN	192.168.50.0/24	192.168.0.0/16	WAN
Y	LAN clients to WGC1	192.168.50.0/24		WGC1
Y	All clients to WGC2	192.168.0.0/16		WGC2

I know I have limited networking knowledge and there is an obvious mistake here. I thought "Local IP" meant the IP assigned to the device and "Remote IP" meant the IP the device is trying to connect to. If this is incorrect, what are the definitions of these terms?

On the third row, I have 192.168.0.0/16 because clients on the guest network have a different IP range, like 192.168.101.*, and I also want them to go through the VPN. It is also a backup VPN client in case WGC1 is down for clients with the IP range 192.168.50.*

 

[ColinTaylor]

Traffic to a local IP address is never routed. Therefore because it doesn't go through the router you don't need any rules for it.

Routing either works or it doesn't. You don't "eventually lose access". When this happens next check whether you can still access the router by IP address, e.g. https://192.168.50.1:8443 If you can it may just be a DNS issue.

I suggest you remove your 1st and 3rd rules and see how it goes.

 

[ssh]

Thanks. I can access the router by IP address right now, and I made the changes. It still appears to work.

I guess it's because on the VPN, I'm using the VPN's DNS servers, so it can't resolve https://www.asusrouter.com:8443/ ?

 

[ColinTaylor]

I guess it's because on the VPN, I'm using the VPN's DNS servers, so it can't resolve https://www.asusrouter.com:8443/ ?

Correct.