Feature Request: support more than one non-guest SSID

TL:DR so apologizes in advance if this was stated already.  True story:

I used to sell Palo Alto firewalls and had one in my home i got for free.  We had very young kids so we got a couple of Hickvision 1440p cameras and put them on the network.  My PANW revealed that these cameras were sending out an SSL connection to an IP address in CHINA!  As such, I got in the habit of turning them off when in use, but they HAD to be on the home network itself as the viewer was on an ipad in the master bedroom.  Add the whole Ring hacks and the common knowledge that DDOS attacks are often from poor/no security iot devices, and there is real merit for a second SSID that is separate from your home.  I would include home automation on this too (actually, an argument for a 3rd ssid separate from the IOT), as you really dont want any former employees/dog sitters./etc) to know your password and changing it on iot devices en masse is a fierce pita.  This is a critical need, and it seems you could even have a way for you to know when it is sending traffic to china and warn us in the apps.  This could be a great selling point.  

NOTE that there should also be an ability to "leak" from a device on one SSID to another else in order to control an iot or airplay to it would require moving to the iot ssid.  Being able to allow a specific IP on one SSID leak to the other would be cool.  That said, let's just start with a second hermetic ssid, on which clients CAN talk to each other so device sharing and control can happen but not on the same network that has your Quicken PC.

I am guessing the resistance is because you would need to have VLANs on the device if wired in order to segregate which could cause support headaches (refer to youtube and put a training there), but it is very important,  PLEASE give us SOMETHING or I am predicting wifi 6 upgrades will go to another vendor.

Thank you

/offsoapbox/

I just had an epiphany on this...  how can AMZN effectively deep spy on us if the echoes are cordoned off to *only* listening to us?  

3 years ago and still under consideration :o ?

Im still holding out hope on this request, one of the older ones for sure...

i'm also hoping to have this feature. 

Supposedly it should mean that a IoT zone that cannot initiate connections to out-of-the-zone with optional certain manual overrides (e.g. exposing say a NAS's SMB, Plex server), plus whatever necessary for mDNS discovery; meanwhile the regular zone has full access to IoT zone devices.

This would be a very good addition for securing the network from IoT attacks. 

Would love to see this.  On my current Asus router, I have 3 guest networks.  (ASUS' firmware actually allows for 3 2.4ghz guest networks + 3 5ghz networks).

1. For IOT devices, no local access granted.

2. For IOT devices, who need local intranet access, but only to devices on this wireless network (Google home devices need this, among others, if you want to use your phone to control them).

3. For actual guests, visiting the home, no local access granted.  Don't want them mingling in the IOT network.

Yes, somewhat excessive, but the separation has purpose.

In its current form, I would only connect the eero to my existing router's LAN port and use it for just the IOT devices.

Wow... very old thread... and NOTHING from EERO... zero from EERO! 

It may be time to revert back to Asus for WiFi... they actually have a product (mesh compatible) that was designed with security in mind.. and works!

Yeah, you may only be preaching to the choir on this issue-

me thinks they consider their product to work well enough (similar to other vendors) that giving us the control we think we need to survive would only muck up a fine product, as I have found to be true in my case. YMMV

Just read a number of reddit threads looking for something that was going to tell me how to setup multiple private networks across the eero mesh. The thread doesn't tell me how to do it, but it does make clear that 4 years after the first request with no movement on this i'm probably better off buying  equipment that already supports what's needed.

A year of WFH, and while I was able to put that computer equipment on a seperate network by putting it behind a spare router, i'm stuck with physical location having to be within range of that single router despite having setup a eero mesh throughout the house.

Agreed this would be useful. Or allow the option to turn off isolation on the guest network so that devices on the guest network can interact with each other.

This topic has some age on it. It is obvious that eero/Amazon will not be adding the second or more ssid option. It is time to move on to a more accommodating solution. This would be so easy for their developers to add it is ridiculous that they have not offered it yet. I so wish I had done more research. 

Why no comments eero? Why no explanation? In all sincerity do you even read these comments? 

Shameful and unbelievable that this gap exists after 5+ years.  Thanks a lot Amazon for killing off an innovative product by under-staffing/under-funding your product support and enhancement teams.  Can't wait to upgrade to another mesh device with any sense of roadmap

Also see https://community.eero.com/t/x1mj25/802-1q-vlan-trunking and https://community.eero.com/t/q5tpsm/implement-vlan (both of which are also 5 years old).

I really wish eero would implement this.  The sad thing is a $30 access point from TP-Link support multiple SSID’s, but eero can’t or won’t implement it.

As a service provider, having a hidden SSID only managed from Insight would be useful so the customer doesn't accidentally change the wifi settings and cut the access to the set top box (IPTV) in doing so...  VLAN association would be a nice to have to.