Guest network subnet - when will this be fixed?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
When will TP-Link finally fix the firmware so that the guest network is on a different subnet to the main network?
I understand that devices on the two can't see each other, but it is nevertheless bizarre that they're in the same subnet.
I run the guest network for IOT devices (not controlled through the deco). I have a computer running HomeBridge, which connects to the guest network with wifi (to control IOT devices) and the main network with Ethernet (to expose the devices to HomeKit).
The computer also serves other purposes, and so needs to locally access other devices on both the main and guest networks.
This causes routing issues, as the computer can't work out which devices are on which interface, since they're both running in the same subnet.
How is it possible that, despite complaints about this absurd design flaw having been made for several years, this is still not fixed in the firmware?
Every other vendor seems to have been able to implement this properly.
The Decos are otherwise excellent, so this is incredibly frustrating
