Use the search feature, both questions have been discussed before with respect to 3006 firmware's Guest Network Pro.How will I now be able to force guest networks to use custom DNS server, meaning my Pihole?
And, there is no way to block internet access to guest networks?
Thank you bennor.. Im just going crazy now because my security cameras won't connect and this update has messed me up. Just a bit frustrated because it was working without any issues for a long time.Use the search feature, both questions have been discussed before with respect to 3006 firmware's Guest Network Pro.
See this post with an example of how to block Internet Access for a Guest Network Pro client:
https://www.snbforums.com/threads/a...ta-is-now-available.94366/page-31#post-954111
See this post for using DNS Director to have Guest Network Pro profile use Pi-Hole:
https://www.snbforums.com/threads/a...ta-is-now-available.94366/page-22#post-952815
One can also use custom scripting to add iptable rules using the firewall-start file to do various things with Guest Network Pro clients. For example see this post on scripting with 3006:
https://www.snbforums.com/threads/t...st-network-pro-limitations.94438/#post-952345
Guest Network Pro/VLAN/SDN is a major feature inclusion that will take one some time to understand how it works compared to 3004.388.x firmware.Thank you bennor.. Im just going crazy now because my security cameras won't connect and this update has messed me up. Just a bit frustrated because it was working without any issues for a long time.
No. One can still use the LAN DHCP DNS fields to assign Pi-Hole to the clients that contact the router for their DHCP address/DNS servers.Regarding using DNS Director for Pihole, does that mean setting pihole IP in the LAN DHCP section is now useless?
See my prior post for where Pi-Hole themselves say to input the Pi-Hole IP address into the LAN DHCP DNS server field, not the WAN DNS field. When you input the Pi-Hole IP address into the LAN DHCP Server DNS field, any main LAN client that contacts the router to obtain it's IP address (and DNS server) will receive the Pi-Hole as it's DNS server. Just make sure to set "Advertise router's IP in addition to user-specified DNS" to "no" to avoid having the router included as a DNS server when using Pi-Hole.So what means I will have to setup each device that connects to my router and point it to Pihole individually? Whereas before, Pihole was set as the default DNS for all devices.
ThanksThe correct notation would be 192.168.53.0/24 and not 192.168.53.1/24 ?
Please correct me if i'm wrong
Even if you update to development branch some scripts maybe less useful going forward. While YazDHCP can be made to work on the main subnet to remember static/assigned IPs it doesn't remember/ backup static IPs on VLANs/ guest networks if they are not on your primary subnet.Reposting a reminder for people to check the following link for addon compatibility with the 3006 firmware:
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006
YazFi as mentioned earlier in this release thread is not supported under 3006, several other scripts likewise may not be supported. Others need to be manually updated to their develop branch.
Instead of repeating what doesn't work, you should show some screenshots with your settings.None of my wireless security cameras want to connect to any of guest networks at all. This is so incredibly frustrating!
I think it has something to do with how Guest Network Pro works. On older routers that don't support Guest Network Pro and only support Guest Network you could ping and access devices on the Guest Network from the Main Network but they couldn't connect to devices on the Main Network.So in order for the wireless devices to be able to connect, I need to enable Intranet access?
This is the only way I am able to make my security cameras connect to the wireless network. What is the point of segmentation if in the end the devices will be able to access the main network?
What am I missing here?
No problems here with having numerous wireless devices (phone, computer, streaming devices, cameras, smart plugs, smart bulbs, Alexa devices, etc) connect to WiFi when there is no intranet or internet connection (for what ever reason) on the 3006.x firmware (both stock Asus and Asus-Merlin). In my case I use WPA2-Personal (not WPA2/WPA3), don't use Smart Connect, and set specific WiFi channels.So in order for the wireless devices to be able to connect, I need to enable Intranet access?
This is the only way I am able to make my security cameras connect to the wireless network. What is the point of segmentation if in the end the devices will be able to access the main network?
Yes, certain scripts are less useful due to the changes that have come with the 3006.x firmware. YazDHCP is a good example where while it works, it had some limitations. YazFi is another. YazFi is not supported on 3006, and is essentially deprecated for the most part due to Guest Network Pro and it's various features that are similar to some YazFi features. Currently there are workarounds to some of the things YazFi could do but Guest Network Pro cannot (like scripting one way to guest for example).Even if you update to development branch some scripts maybe less useful going forward. While YazDHCP can be made to work on the main subnet to remember static/assigned IPs it doesn't remember/ backup static IPs on VLANs/ guest networks if they are not on your primary subnet.
I had to do a factory reset on the router. I use Blue Iris NVR and if I do not provide access to Intranet to the wireless cameras, Blue Iris will not see them. As soon as I give access to Main Network, they immediately pop up in Blue Iris.Yes, certain scripts are less useful due to the changes that have come with the 3006.x firmware. YazDHCP is a good example where while it works, it had some limitations. YazFi is another. YazFi is not supported on 3006, and is essentially deprecated for the most part due to Guest Network Pro and it's various features that are similar to some YazFi features. Currently there are workarounds to some of the things YazFi could do but Guest Network Pro cannot (like scripting one way to guest for example).
If you don't provide detailed information about your setup and settings, no one can help you.I had to do a factory reset on the router. I use Blue Iris NVR and if I do not provide access to Intranet to the wireless cameras, Blue Iris will not see them. As soon as I give access to Main Network, they immediately pop up in Blue Iris.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!