VPN Policys not working with Wireguard and Flint 1800

Other topic as it was mentioned above: regarding Netflix / Primevideo / Disney+ these are the domains I “steer” via VPN policy and/or client proxy file on router in www dir.

/* disneyplus.com */
bamgrid.com
bam.nr-data.net
cdn.registerdisney.go.com
cws.conviva.com
d9.flashtalking.com
disney-portal.my.onetrust.com
disneyplus.bn5x.net
js-agent.newrelic.com
disney-plus.net
dssott.com
adobedtm.com

/* Amazon Prime Video */

aiv-delivery.net
us-east-1.aiv-delivery.net
ters.us-east-1.aiv-delivery.net
fls-na.amazon.com
fls-eu.amazon.com
api.us-east-1.aiv-delivery.net

completion.amazon.com
m.media-amazon.com
aiv-cdn.net
aiv-delivery.net

atv-ext.amazon.com
atv-ext-eu.amazon.com
atv-ext-fe.amazon.com
atv-ps.amazon.com
atv-ps-eu.amazon.com
atv-ps-eu.amazon.co.uk
atv-ps-fe.amazon.co.jp
atv-ps-fe.amazon.com
primevideo.com
pv-cdn.net

/* Netflix */
flxvpn.net
netflix.ca
netflix.com
netflix.com.au
netflixdnstest10.com
netflixdnstest1.com
netflixdnstest2.com
netflixdnstest3.com
netflixdnstest4.com
netflixdnstest5.com
netflixdnstest6.com
netflixdnstest7.com
netflixdnstest8.com
netflixdnstest9.com
netflixinvestor.com
netflix.net

netflixtechblog.com
nflxext.com
nflximg.com
nflximg.net
nflxso.net

2 Likes

Wait a while for us to update 4.0.2 firmware for AX1800.

1 Like

This was the trick for. I had found aiv-cdn . net, amazon . com ssl-images-amazon . com and media-amazon . com using the “Sources” tab in the Inspector in my browser but needed some more to whitelist when using a Samsung TV, once I added the ones you found it worked.

1 Like

FYI, to get the ESPN Roku app to work I added these domains to bypass the VPN (Proton Free in my case):

espn . com
espnplayer . com
espnplus . com
espncdn . com
espn . net
adobe . com
disneyplus . com
bamgrid . com
nr-data . net
go . com
conviva . com
flashtalking . com
bn5x . net
disney-plus . net
dssott . com
adobedtm . com

I added spaces before and after the . in this post so the forum doesn’t think I’m trying to spam the post, you will of course need to remove those extra spaces

I was never able to get VPN Policies to work properly with Wireguard client connections on the x3.x releases. OpenVPN worked well, but not Wireguard.

Environment:
Brume MV-1000 v3.216 firmware.
Adguard Home v0.107.38

image

The Wireguard+Adguard Home+VPN policy issue has been resolved in the v4.3.8 beta release in my experience. The v4.x UI will also warn you of various configuration settings that will break VPN policy, unlike the v3.x series.