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
Right now I'm not using DECO's guest network at all anymore, which is quite sad.
My current situation:
* DHCP is done by the router.
* DNS is done by an internal pi.hole in the main network.
* The router forwards all DNS requests to the pi.hole. The pi.hole only gets requests from the router.
I noticed that guests (who are connected to the Deco guest network) could still access devices from the main network.
That means the guest network is not isolated at all. Maybe this has changed with one of the deco updates, I don't know... My deco setup has always been in "Accesspoint mode".
Because of this, the guest network is completely useless, and shouldn't even be named a guest network. It's just a second SSID that can be used to connect to the exact same network.
So now I'm using my router's guest wifi for the guest network. Of course, with less coverage than the mesh system. But at least it's isolated.
After waiting several years, I don't think we'll ever get a solution, even though the amount of complaining users is more than enough to consider it.
@TP-Admin @TP-Link it would be nice to at least have a clear response though...
- Copy Link
- Report Inappropriate Content
@BenVA with my deco M4's the guest network is correctly isolated and that's why it can't access my Adguard DNS server. Therefore, an easy fix for me would be to be able to configure other DNS settings for the guest network.
- Copy Link
- Report Inappropriate Content
When the Deco is in AP mode, for some stupid reason it doesn't tag the outbound guest traffic with the guest VLAN. Guests are isolated within the Deco itself (can't reach another wireless client) but out the LAN port... yeah, that isolation is lost. It's SUPER stupid. There is a feature request to fix this -> https://community.tp-link.com/en/home/forum/topic/546942
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
It's 2023 and I can't let my pihole include my guest network with tp-link? Ridiculous.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@GeorgeBark my suggestion is to do what I did. Get rid of your TP Link Router and buy an ASUS one. All my problems went away.
- Copy Link
- Report Inappropriate Content
@TP-Link count me in. This is absolutely needed
- Copy Link
- Report Inappropriate Content
Information
Helpful: 136
Views: 30650
Replies: 194
Voters 124
