DNS Server Settings and Priority with Guest Network Pro?

[jksmurf]

Apologies if this has been covered before, I didn’t quite find a simple explanation for my feeble brain, it’s 3am, can’t sleep.

This came about because I happened to be on my IoT SSID and noted I was getting adverts (I use Diversion). I don’t get these on my main network.

• I currently do not have any values in LAN/DHCP as the tool tip says you can leave it blank.
• I currently have WAN DNS set to cloudflare and I have the same cloudflare settings as DNS for my IoT network.

With GNP, the presence of the ads on the IoT network had me starting to wonder if I’ve configured one or more of these three locations incorrectly?

Is my understanding correct, that if you route the IoT network via the primary lan that will also block ads? If so, which settings should I change? Should I leave the IoT DNS blank and assume it goes through primary? I’m a wee bit confused as to order and priority. I do not recall the old Guest Network having DNS settings.

 

[bennor]

What does the IoT client indicate it's DNS server(s) are? Do they match what you have configured in the Guest Network Pro Profile's DNS fields? It would appear that by using the same DNS addresses in the Guest Network Pro Profile's DNS fields you may be bypassing the router's Diversion. Try removing those Guest Network Pro Profile DNS values and see what happens. Or set them to the router to see if Diversion kicks in and blocks ads on the IoT devices.

Are you using DNS Director? You can enable DNS Director and set the DNS redirection rule for Guest Network Pro Profile(s) to router which I assume would then route to Diversion.

 

[ColinTaylor]

Apologies if this has been covered before, I didn’t quite find a simple explanation for my feeble brain, it’s 3am, can’t sleep.

This came about because I happened to be on my IoT SSID and noted I was getting adverts (I use Diversion). I don’t get these on my main network.

• I currently do not have any values in LAN/DHCP as the tool tip says you can leave it blank.
• I currently have WAN DNS set to cloudflare and I have the same cloudflare settings as DNS for my IoT network.

With GNP, the presence of the ads on the IoT network had me starting to wonder if I’ve configured one or more of these three locations incorrectly?

Is my understanding correct, that if you route the IoT network via the primary lan that will also block ads? If so, which settings should I change? Should I leave the IoT DNS blank and assume it goes through primary? I’m a wee bit confused as to order and priority. I do not recall the old Guest Network having DNS settings.

IIRC this has already been discussed in the addons forum. I think @dave14305 provided a workaround for the problem.

 

[jksmurf]

What does the IoT client indicate it's DNS server(s) are?

Not sure where I find these?

Do they match what you have configured in the Guest Network Pro Profile's DNS fields?

It would appear that by using the same DNS addresses in the Guest Network Pro Profile's DNS fields you may be bypassing the router's Diversion. Try removing those Guest Network Pro Profile DNS values and see what happens. Or set them to the router to see if Diversion kicks in and blocks ads on the IoT devices.

Will do and will get back to this thread.
[EDIT] that’s a no, it doesn’t work. Set it to Default, hit apply, joined IoT SSID again, got ads.

Are you using DNS Director? You can enable DNS Director and set the DNS redirection rule for Guest Network Pro Profile(s) to router which I assume would then route to Diversion.

Nope not using that. Never found the need to.

 

[jksmurf]

IIRC this has already been discussed in the addons forum. I think @dave14305 provided a workaround for the problem.

Thanks will try to find it if Dave hasn’t cropped up by then.

 

[bennor]

Not sure where I find these?

You would check the network settings of the client device connected to the IoT network to see what it indicates for DNS servers. Some IoT devices hard code their own DNS servers which can potentially cause the IoT device to bypass the router. One solution to that bypass issue is to use DNS Director to force all Guest Network Pro Profile client to use a specific DNS server or use the router.

 

[ColinTaylor]

Thanks will try to find it if Dave hasn’t cropped up by then.

This is probably the thread I was thinking about:

Diversion - [SOLVED] Diversion Guest Network Pro - blocklist applied to multiple SSID

Does Diversion work with Guest Network Pro Profiles / Vlan? If yes, is there any additional configuration outside of what the Diversion script does? Reason I ask is, it appears Diversion works as expected for the Wireless Network SSID (Main Network), but not for the additional SSID / VLAN...

www.snbforums.com