Domain based VPN policydoes not work on AX1800 Flint

[bring.fringe18]

Upstream/Public IP

Policy

Results

[vinnfts]

That’s extremely weird, I don’t know why mine does not working!

[bring.fringe18]

Have you disconnected & reconnected WG Client?

@bring.fringe18

I had to disconnect & reconnect WG Client for policy additions/edits/changes to take effect.

[vinnfts]

I did multiple times

[bring.fringe18]

I’d reflash via U-boot. Nuke it all; start over. That’s all I can tell 'ya.

[scumball]

I have the same issue on my mt2500
whatismyip.com is the only domain in the policy
Whenever I visit that site I see my ISP and ISP assigned IP

[alzhao]

@scumball and @vinnfts can you pls post screenshot as @bring.fringe18 do?

[vinnfts]

I did @alzhao
Public IP

Policy

Result here

It looks like the policy does not work although the Wireguard VPN is running successfully here

[alzhao]

You are putting the policy wrong.

You only need to put ipecho.net, not https://ipecho.net

[vinnfts]

@alzhao No, I did both, nothing worked

[alzhao]

Pls just post exact steps and results. Otherwise too difficult to check.

[scumball]

No VPN

VPN On, one address and it WORKS

Then when I add more addresses to the list, it STOPS working again

[alzhao]

I did the same test, step by step as yours, here is the result.

1. Browser has DNS cache, even in Private Mode. Flush dns of Windows does not fit.
2. You can wait a while until your browser and windows to flush dns. Or you can use two browser, close the browse completely and open again to test.

[bring.fringe18]

Windows 10 via Command Prompt: ipconfig /flushdns :

Successfully flushed the DNS Resolver Cache.

[alzhao]

@bring.fringe18

Windows 10 via Command Prompt: ipconfig /flushdns :

This does not affect browser

[bring.fringe18]

@scumball was also running traceroute within Windows so it’s better to clear the whole slate, no?

I had no issues using Brave’s Private Mode, as the screenshots show, FWIW.

[alzhao]

Do both. Flush dns of windows. Close browser and open again, using private mode.

[scumball]

Ok will retest. I also tried speedtest on my Apple TV and was seeing my ISP provider not VPN. So maybe it takes time to register on the router?

While I have your attention, do you have any ideas on my other thread.

When I run the VPN based on clients or global policy it uses my slower failover connection only and not the main active connection?

MT2500 Wireguard connection using wrong route

I have two connections on my MT2500, a fast WAN connection and a slower TETHERING connection 192.168.0.254 is the fast WAN 192.168.1.254 is the slow TETHERING (set as FAILOVER) I noticed on the VPN it would only ever connect at a slow speed When I run ip route show - it shows the VPN connection tied to the slow eth2 route How do I fix this, and get the VPN connecting through eth0? 0.0.0.0/1 dev wgclient scope link default via 192.168.0.254 dev eth0 proto static src 192.168.0.1 metric 10 de…

[scumball]

When using domain policy VPN on my brume2 I can see on a tracert from a connected PC that the route is going via VPN but I see no traffic on the status page and in Luci when streaming from that domain. Why would that be?

I also see when using tracert on the brume itself (SSH) that everything is going via the VPN not just the domains on the list.

Not sure this is working correctly…

Also still have an ongoing issue when using multi WAN that the VPN always defaults to the failover connection and not the default primary connection.

[alzhao]

@scumball

I also see when using tracert on the brume itself (SSH) that everything is going via the VPN not just the domains on the list.

Pls post details of your test steps and result, with screenshots.

@scumball

Also still have an ongoing issue when using multi WAN that the VPN always defaults to the failover connection and not the default primary connection.

This will be added in firmware 4.5.x