Feature Request: support more than one non-guest SSID
With more IoT devices in the home, security is becoming a huge concern with the attacks that are possible.
I'd like to see eero support more than one non guest SSID so I can isolate my IOT devices away from other sensitive devices like laptops and servers.
I could use the guest SSID that's currently available but I want to not have guest devices be able to interact with those devices
One way is to just add another SSID option, in addition to the one that's possible already. However I'd love to see eero adopt Google wifi's approach which seems to be really unique.
Google allows a second SSID (call is SSID2), but all devices on it can be access from SSID1 (but not the other way around). This is crucial to not break scenarios where these IoT devices need you to have access to them but don't want to have hassle of switching wifi networks.
Jeff C. cMoo92
Could we have a status update on this topic? It's been "Under consideration" for 3 years now.
I keep seeing other similar requests come up, like this one:
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.
Having first replied to this thread almost 3 years ago.... And with the new WiFi 6 changes... I am at a point, that I am done purchasing Eero hardware new. If I add anything else to my network, it would be used nodes that I get for cheap. That if I can make it that long. I just added 5 new IoT devices in the last two weeks. With TV's, Game Systems, Security Cameras, iOT devices, phones, tablets, computers. Right now, at this minute, I am utilizing 164 IP's on my home network. 50 of them are IoT devices, that I could put on another SSID with no utilization changes.
And then when I need WiFi 6, it will be another vendor, that supports at a minimum 2 secure SSID's on the same hardware. (hopefully it would be more then 2, but I would be happy with at least two). I don't want to run two systems in my home. I would like to also have wired nodes, that use PoE, so I don't have to run both hardline to the node, and power.
It is almost 2021, and see the new hardware line up, very disappointed. There are many other features that I would like to have, but bottom line... just looks like eero has stopped innovating, and just using their name recognition going forward. These devices are WAY to expensive at this point, for being steps behind competitor features.
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.
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.
Here's another use case in addition to the IoT ones mentioned. I have the same IoT concerns, but my situation just became a bit more real and sensitive. I'm literally having solar panels installed on my roof as I write this. The solar panels and controller need a wifi network for communicating externally and providing data for the company that services them as well as providing statistics and eventually controller information when it will be connected to my wall batteries. In order to do this, I need to provide an SSID and password. So now my network password for my Eero system is going to be in the hands of someone outside of the family. Without a second SSID and password, I have to hand over the keys to the kingdom. The guest network won't work because the Enphase controller needs to talk to the solar panels and the guest network (rightfully) does not allow peer-to-peer communication.
Eero, please consider supporting a second or even third SSID for the Eero mesh network. I would love to separate device-type traffic from one and another.