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
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@TP-Link You are losing customers by not fixing this. You might think a few people ditching your products because you refuse to fix your mistakes is meaningless.
However, the customers you are irritating to the point of trashing your devices (and buying from your competitors) are your most technical customers.
These are the customers that influence the buying decisions of their family and friends.
These are the customers most likely to work in the industry; they will remember your indifference to fixing consumer devices and will avoid your commercial products as well.
- Copy Link
- Report Inappropriate Content
I have the same issue, running a local PiHole DNS server.
I was able to circumvent the problem by connecting the PiHole directly to the ISP-modem, outside the Deco network. See https://community.tp-link.com/en/home/forum/topic/873060?replyId=1728126
It's a shame though that such a basic feature is missing in the Deco configuration.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I've not tried it with NetworkManager, but I think it should be possible.
The reason for networkd, was to use networkd-dispatcher for the iptables script.
But actually, in recent distro, we have nftables (and the iptabes commands are just converted by the OS).
So instead of the networkd-dispatcher script, we can create nftables rules like:
/etc/nftables.d/10-guest-network-dns.conf:
```
table ip mangle {
chain PREROUTING {
type filter hook prerouting priority mangle; policy accept;
iifname "eth0.591" meta l4proto { tcp, udp } th dport 53 meta mark set 591
iifname "eth0.591" meta l4proto { tcp, udp } th dport 53 ct mark set mark
}
chain OUTPUT {
type route hook output priority mangle; policy accept;
meta l4proto { tcp, udp } th sport 53 meta mark set ct mark
}
}
}
```
and start service to manage the config:
sudo systemctl enable --now nftables
hope it helps :)
- Copy Link
- Report Inappropriate Content
NetworkManager also has a "NetworkManager-dispatcher"...
I'm running Trixie in my RPI... I'll give it a try...
Edit: No luck so far... cant figure out how to make this work...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 195
Views: 94661
Replies: 278
