Wireguard Server blocking random sites

[Asus79]

I have a WG server on my AX-86U running Merlin. My peers are a GL-inet travel router and my phone. I have access to LAN from remote, and some webpages but not all. Google, Reddit, and webmail sites are blocked. Bing, news and sports sites work.
I am trying to run the WGS traffic through my AX-86U router WG client NordVPN. I have tried different DNS including google, Nord's and the router's ip address on the peers. I have also tried running the traffic through WAN, and both with and without allowed DNS access.

 

[ZebMcKayhan]

I have a WG server on my AX-86U running Merlin. My peers are a GL-inet travel router and my phone. I have access to LAN from remote, and some webpages but not all. Google, Reddit, and webmail sites are blocked. Bing, news and sports sites work.
I am trying to run the WGS traffic through my AX-86U router WG client NordVPN. I have tried different DNS including google, Nord's and the router's ip address on the peers. I have also tried running the traffic through WAN, and both with and without allowed DNS access.

The only thing that comes into mind is perhaps ipv6 issues. Do you have ipv6 enabled on the router?

 

[Asus79]

The only thing that comes into mind is perhaps ipv6 issues. Do you have ipv6 enabled on the router?

I have IPV6 turn on only to connect the router to my VPS because I'm behind GNAT. I do not have IPV6 Nat turned on.

 

[ZebMcKayhan]

I have IPV6 turn on only to connect the router to my VPS because I'm behind GNAT. I do not have IPV6 Nat turned on.

I have had issues in my setup and the problem was that the router gives an ipv4/ipv6 to the client, so the client thinks it have both. In my case ipv6 was not working which caused issues. In your case ipv6 may work but through wan and not vpn, so from a different city/country. This is what I believe may be causing you issues.

On the client side, could you try to remove the ipv6 details in the wireguard app for this peer (or make a copy of it and change in the copy). Then start it as an ipv4 only peer. If nothing else, just to see if this changes anything?

 

[Asus79]

I have had issues in my setup and the problem was that the router gives an ipv4/ipv6 to the client, so the client thinks it have both. In my case ipv6 was not working which caused issues. In your case ipv6 may work but through wan and not vpn, so from a different city/country. This is what I believe may be causing you issues.

On the client side, could you try to remove the ipv6 details in the wireguard app for this peer (or make a copy of it and change in the copy). Then start it as an ipv4 only peer. If nothing else, just to see if this changes anything?

My client is set up for ipv4 only. I am using wg-easy on my VPS and when selecting AllowedIPs = 0.0.0.0/0 wireguard freezes my vps client and will not connect. I am using 0.0.0.0/1 which I think may be my problem

 

[ZebMcKayhan]

My client is set up for ipv4 only. I am using wg-easy on my VPS and when selecting AllowedIPs = 0.0.0.0/0 wireguard freezes my vps client and will not connect. I am using 0.0.0.0/1 which I think may be my problem

Hmm ok... the /1 means you only include half the internet (0.0.0.0 - 127.255.255.255).

Are you using the VPS to connect to router wg server and relay clients?
Here is how I did it https://github.com/ZebMcKayhan/Wire...ov-file#setup-private-server-via-cloud-server
(You need to scroll down a little to get to the setup VPS part)
It may give you an idea where your script goes wrong.