So I bought an Orbi RBK43 kit with the intention of using one SSID as my primary, in-home personal device network (phones, laptops, etc.). I also was planning to use the secondary (Guest) SSID as my IoT network, and using the blocking feature to prevent the Guest network from talking to my main/personal network.
However, I have some devices (specifically, Blink cameras) that I am pretty sure need to be able to talk to each other -- the sync module needs to send commands to the cameras. Also, I can easily envision future home automation tools potentially needing to talk to one another on the local network.
Since the Orbi Guest network allegedly blocks intra-network communication, putting devices like this on the Guest SSID would not work. If I instead flip-flop my original plan and use the Guest SSID for personal, and main SSID for IoT, the blocking feature (as I understand it) won't help because I'd still be allowing the IoT network to talk to my personal devices; and if my personal devices needed to talk to something on the IoT network (for example, a printer) then that would also be a disaster.
Is it possible to block the Guest network from reaching the main network, but NOT block intra-zone communications on Guest? Even if it has to be done thru the shell (I'm very comfortable with shell UIs if that's the only way to do it).
Thanks!
However, I have some devices (specifically, Blink cameras) that I am pretty sure need to be able to talk to each other -- the sync module needs to send commands to the cameras. Also, I can easily envision future home automation tools potentially needing to talk to one another on the local network.
Since the Orbi Guest network allegedly blocks intra-network communication, putting devices like this on the Guest SSID would not work. If I instead flip-flop my original plan and use the Guest SSID for personal, and main SSID for IoT, the blocking feature (as I understand it) won't help because I'd still be allowing the IoT network to talk to my personal devices; and if my personal devices needed to talk to something on the IoT network (for example, a printer) then that would also be a disaster.
Is it possible to block the Guest network from reaching the main network, but NOT block intra-zone communications on Guest? Even if it has to be done thru the shell (I'm very comfortable with shell UIs if that's the only way to do it).
Thanks!
