YazFi guest networks stop working when changing DNS or using VPN

[jsn2233]

My router is the GT-AX11000 and firmware is 3004.388.10_2_rog

Firstly, I will preface by saying like an idiot I tried to change the default IP to 192.168.1.1 unaware that this would cause issues with YazFi. I changed it back and the guest networks began to work again.

The issue I have now is that when I force DNS to my pihole at 192.168.50.8 or when I make a rule in VPN Director to redirect the guest network traffic through my wireguard VPN the network stops working - no internet.

As soon as I remove these rules and let the guest network go through the default DNS on YazFi (8.8.8.8) or disable wireguard VPN Director rule, it works just fine. Is there something I'm missing? The default subnet is using my pihole for DNS and is also redirecting traffic to my VPN. No idea why this is happening to my guest networks now. Only had this issue since I changed router to GT-AX11000, I was using the AC86U with an old firmware and my guest network used to funnel to my DNS perfectly before.

Edit: After I changed the default IP of my router back to 192.168.50.1 I removed YazFi and the config files, rebooted my router and then reinstalled YazFi just in case.

 

[jsn2233]

After trying what was listed here for the vpn, the vpn now works for my guest networks! Although you also have to make the script executable which wasn't mentioned in the post (as helpful as it was).

Now I just need to figure out how to make the DNS stuff work.

Edit: nvm it's not working :/
Edit2: nvm it is working, I didn't realise you have to put the the ip entry into REMOTE and not local. Interesting. I don't understand why that works

 

[bennor]

Although you also have to make the script executable which wasn't mentioned in the post (as helpful as it was).

FYI, that post does mention setting the permissions to 0755 which includes execute.
Set the wg-yazfi.sh file permissions to 0755.

PS: A suggestion. In your initial post you have some font coloring applied to the text following "Only had this issue since I changed router to", you may want to remove that font coloring to make that text readable for others.

 

[jsn2233]

FYI, that post does mention setting the permissions to 0755 which includes execute.
Set the wg-yazfi.sh file permissions to 0755.

PS: A suggestion. In your initial post you have some font coloring applied to the text following "Only had this issue since I changed router to", you may want to remove that font coloring to make that text readable for others.

Thanks for the correction and color fix, sorry my linux isn't the best I forgot the numbers in chmod can represent execution permission but any networking help for me?

Your post was so helpful bro! It got it working for me for only wgc1 but I'm noticing when setting my guest networks to any other wireguard client it refuses to work. Only wgc1 is working for some reason. I've added these two rules:

As soon as I change it to wgc2 or wgc3 and update the VPN director rules they stop working but continue working with wgc1. The actual wgc3 is working perfectly, I've changed my LAN to run through it and it works. For some reason the guests are having issues with it and the internet just drops. Got any magic for me?

 

[bennor]

Your post was so helpful bro! It got it working for me for only wgc1 but I'm noticing when setting my guest networks to any other wireguard client it refuses to work. Only wgc1 is working for some reason. I've added these two rules: View attachment 69688
As soon as I change it to wgc2 or wgc3 and update the VPN director rules they stop working but continue working with wgc1. The actual wgc3 is working perfectly, I've changed my LAN to run through it and it works. For some reason the guests are having issues with it and the internet just drops. Got any magic for me?

I haven't experimented with the YazFi/Wireguard since that post in 2024. Pretty much the only suggestions I have is you review your changes from wgc1 to wgc2 including checking or adding the VPN Director entry for Wireguard 2. Make sure the wlx.x matches the one your targeting in YazFi by checking for the correct value in the YazFi config file.

 

[jsn2233]

I haven't experimented with the YazFi/Wireguard since that post in 2024. Pretty much the only suggestions I have is you review your changes from wgc1 to wgc2 including checking or adding the VPN Director entry for Wireguard 2. Make sure the wlx.x matches the one your targeting in YazFi by checking for the correct value in the YazFi config file.

Yeah I did it a million times until my eyes fell out, It seems like some kind of weird bug. Will use ovpn for my other needs as wireguard doesn't play to good with yazfi it seems, I'm sick of trying to fix this now