VPN: Temporarily solve same subnet conflicts

madrian · 2019-08-28T19:06:51.040Z

I am using my Gl.Inet router while I am traveling and I connect to my home with VPN. Sometimes I have problem, when remote subnet is the same as my home subnet (192.168.1.x). Sure, I should change this to something not commonly used range, but I have many devices on my network and I don’t have time to change.

On my PC I am using this temporary solution:

sudo route add -host 192.168.1.10 -interface ppp0

If I want to access home device at 192.168.1.10, it would be accessing trough ppp0 VPN interface.

It is possible to set static route like this on Glinet router?

dzwghx · 2019-08-29T02:23:17.711Z

You can add static routes on Luci.

static-routes1072×646 23.4 KB

madrian · 2019-09-14T18:38:19.343Z

Thank you, I tried to add here, but it’s not working. What I am doing wrong here?

402206×996 439 KB

192.168.9.4 is my Wireguard VPN interface IP address, I want to do a static route trough this interface.

madrian · 2019-09-15T17:13:07.889Z

Anyone?

I added more info here:

OpenWrt Forum – 15 Sep 19

VPN: Temporarily solve same subnet conflicts

192.168.9.4 is the WG0 IP (VPN interface) address. It is connecting to the remote server 192.168.9.1. I tried with IP 9.1 too, but it's not working either. I have these options: I can't see wg0 option here, neither in Interfaces: ...but I...

madrian · 2019-09-16T07:23:54.846Z

Manually specifying ip route trough cli works:

ip route add 192.168.1.99 dev wg0

Any way to achieve this by GUI?

madrian · 2019-09-16T09:12:36.279Z

It would be also OK, if WG client/GUI interface would support PostUp/PostDown options:

PostUp = ip route add 192.168.1.99 dev wg0; ip route add 192.168.1.54 dev wg0; ip route add 192.168.1.155 dev wg0; ip route add 192.168.1.8 dev wg0;
PostDown = ip route del 192.168.1.99 dev wg0; ip route del 192.168.1.54 dev wg0; ip route del 192.168.1.155 dev wg0;

madrian · 2019-09-27T21:42:22.799Z

So, any way to support PostUp/PostDown in Wireguard config? It’s part of Wireguard, but I don’t know if is implemented on Glinet firmware.

alzhao · 2019-09-28T01:54:32.537Z

As this is standard we could add to the firmware. But the best way is to let the firmware do it if there is a good way.

@dzwghx @robotluo

robotluo · 2019-09-29T01:19:52.152Z

In many cases wireguard will not have an UP/DOWN signal and will need to modify the source code or start a daemon

madrian · 2019-09-29T09:45:54.912Z

wg-quick is handling all this:

https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8

No need to modify any source or write a daemon.

At this moment how do you handle wg interface UP/DOWN commands? I think with wg-quick.