Future Consideration Feature Request - Guest Network separate DHCP/DNS settings
Hi @TP_LINK,
I've had rock solid performance so far, and do like the Deco Labs options (although the Wifi Interference check results show 'low' then say underneath that there is significant interference), I do, however, have a feature request to put forward.
My use case:
- 3 x Deco M5s in Router mode
- Several wired and many wireless devices on the main network
- Several wireless devices on the guest network (my work devices)
- DHCP is handled by the Deco, and DNS is served by another server on the main network.
If I set the DNS to only have the DNS server, both the main and guest network use these settings. This causes the guest network to fail as it is segregated from the main network where the DNS server resides.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@NachoGtz When I set Pi-Hole as the router's DNS server on my local network, the router gets confused and reverts its IP address to 192.168.1.1 (when I had it configured for 10.0.0.1). Yet another frustration.
- Copy Link
- Report Inappropriate Content
I would also find this feature invaluable.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Upvote this! even tough, I believe I will no longer have my M9+ when (and if) it comes... looking already for alternatives...
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Add me to the 'me too' list for more Guest Network control and configuration options.
I run AdGuard to provide local encrypted DNS and more parental control for my kid. But I don't want to give her little friends access to the Main network when they visit with their phones and tablets to play Roblox, or anyone else. I'd also prefer to connect my work computer to the Guest network.
Options that would work:
- Allow custom DNS options for the DHCP server on the Guest network (to allow defining public DNS for Guest network devices only)
- Make DHCP for the guest network completely separate from the Main, with it's own subnet/IP ranges, DNS settings, etc.
- Allow granular control such that specific devices (DNS servers, printers, etc) on the Main network can be made accessible from all devices on the Guest network.
- Allow granular control such that specific devices on the Guest network can be given access to specific devices on the Main network.
- Allow granular control such that specific devices on the Guest network are accessible from all other devices on the Guest network (ie, I could put another AdGuard instance on my Guest network)
Today, the Guest network is mostly useless.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Not understanding why this kills the network. At the very least it should relay the DNS protocol.
Very disappointed. I need this feature or better yet open up the software and let me flash it myself along with the 50 other basic things these systems are lacking.
- Copy Link
- Report Inappropriate Content
another +1 to the feature; it's quite critical to make the guest network useful at all
- Copy Link
- Report Inappropriate Content
Information
Helpful: 131
Views: 28902
Replies: 188
Voters 119
