Orbi Pro 6 - IOT Client Isolation

Frank,

Hope the below helps.

Everything on SSID 1 (admin) can see and (via app) talk to those on SSID3 (IoT).  But not the other way around.  So with SSID iphone, I can tell a irobot on SSID 3 to vacuum via the app on the phone.  I can monitor and change my IoT Thermostat, etc.  This is done via an iphone app where I have entered the IP address for each device, or physically on the IoT device where I can setup a fixed the IP address (Nexia Thermstat), or the decvice website that contains the same fixed IP address.    All of these IoT devices have fixed addresses that I use from my reserved pool, i.e., below the starting point for the DCHP addressing.  DCHP addressing normally starts at __.___.__.02. I start at 51 or 101 to allow me to assign 50 or 100 devices that will always have th esame iP address.

(Normally) Alexa Echo DOT etc (SSID IoT) cannot see an external speaker on SSID1 or broadcast to it.  If on same SSID, speakers can be connected to various sats or the main router and play normally.  A phone on SSID 1 can make changes to an Echo DOT on SSID IoT, but again that is because you ise an app that knows the IP address of the Echo DOT.  I say (Normally) because I have not tried to look for app settings that would allow me to specify a IoT IP address.  That probably wll not work, but have not tried - something to attempt in spare time.

Hardwire connections to devices and switches are all SSID1 by default.  My TV, roku, sat receiver, AV receiver etc are all hard wired.  My Echo DOT cannot see or communicate with them but my SSID wifi phones etc can stream or airPlat to any of them regardless which Orbi SAT or Router phone is connected to.  My AV receiver has wifi, but terrible location so use wired that has been there for years.  That locks all related wifi speakers to SSID1, or they will not be seen.  but I do not want Alexa Echo DOTS etc anywhere near SSID1, so Echos ater IoT SSID.  All mics and cameras on SSID1 off by default.