153Feature 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.
-
Also, even better if the SSIDs also supported VLAN so those of us that use eero in bridge mode, can segregate traffic with a separate router.
-
Concur.
request Multiple SSID and VLAN assignments for each to allow separation and filtering of Guest / Family / IOT / Main Network.
-
I would like to see the ssid2 feature as well. With several ip cameras, weather station, streaming devices/TV, etc... it would be nice to keep them from being visible to my computers but still able to access from the computer.
-
Thanks for sharing this feature request, tmchow 😀
It is great to see others already chiming in.
-
Jeff C.
I just reached out to Eero on Twitter for this feature. https://twitter.com/eerosupport/status/1083386235312373766?s=21
so glad to find this thread and other users supportive of this idea.
I see it’s under consideration. Any idea when it will be approved or rejected? It seems like this thread is 2y old...
-
-
Another +1 to this
-
+1!
-
+1 on this.
I have not purchased EEROs yet and was researching whether multiple SSIDs were possible. With more and more IoT, streaming devices and sophisticated attacks, it would be great to be able to segment traffic, especially for regular WiFi users that would be super easy to setup. As an advanced network user, I could implement this using a separate switch, but isn't it the point of EERO to be an extremely easy to use solution.
As I have not read the manual, I don't know if this is also able to restrict traffic as an advanced firewall would be able to do, such as only permit http, https, dns, etc...
For me, this would be a slam dunk to purchase this product. For now, I will wait to see what develops in the market.
-
Can I add ++++++++10000 to this. I believe this would totally take this to the next level. In my current house, we use well over 100 IP address, and sometimes more. my IoT devices: Nest, Nest Protect, Nest Cams, Ring, August, WeMo... are 20... then get to Alexa, Garage Door, VoIP... and growing... While we are not the majority of users out there, we are going to be a growing number. Having a 2nd SSID that can be on a second subnet. So that it can get it's own range of internal IPs, as compared to Phones, Tablets, TV's, Gameing systems... will allow us the flexibility to isolate, and QoS in bulk.
It maybe us geeks right now, but each year... more and more devices (like Refrigerator, Stove, Washing Machine) want a WiFi connection... Since we are probably a generation or more away from getting rid of IPv4, and going to full IPv6 support... we have to do what we can.
I personally wire my eero's together, as I designed my house that way 15 years ago... I know I am exception. If I have to by a bridge device, or even replace the eeros with new hardware... Okay... I can do that... but I don't want to have to install an entire second Mesh-Wireless system. -
+ 1 on this topic for all the reason mentioned already. With the price point and functionality as is - this would be a value add for existing customer that want more out of eero products. All we are looking for is separate SSID that affords its own broadcast domain (subnet) - we can leave the routing to an external device so its easier on the feature request.
-
Need to bump this again... As I ad another 10 or so devices, since September till year end... My network is soon going to really need two secure SSID's, where I can have two subnets. I REALLY don't want to introduce another set of beacons/hardware, as one of my desires for going with eero and mesh, so I can reduce my radio frequency noise for my home and neighborhood. (I can see almost 20 different WiFi networks here in my home, it is getting very noisy)
-
I have two ISP connections, one DSL and the second Satellite. I use a Cisco 1811 router to manage device connections and vlans in my home network. I have 4 euro devices located throughout the house. I subscribe to eero plus for additional protection. I would love it if my euro network could support two VLANS with separate SSID's so that I could assign clients to the ISP I want them to use. Really would love to see this feature added to a great system!
-
+1
-
Jeff C. This seems like a feature that it very highly desired by your user population. Could we get an update on whether this is planned for a future release? I'm certainly highly interested in it (to the point of considering a jump to Google WiFi instead).
-
Any updates here? 😿
-
I signed up for the forums just to bump this topic. I'm switching to an Eero system very shorty (already own the hardware) and agree with tmchow that this feature would be extremely welcome.
It seems like I read about smart devices being hacked every day now, or older smart products that were abandoned from a support stand point and are now susceptible from a security stand point. For a while I told myself when I set up my Eero's I was going to put all my smart devices on Eero's guest network. I didn't feel like it was ideal because actual guests would also be using that network, but I figured it would be better than having possible insecure devices on the same network as my computers.
I never thought about tmchow's other point about having to switch networks to control these devices. That would be a major hassle and something I never considered. The way tmchow describes how Google handles it seems great, with a secondary SSID that separates the networks but that the primary SSID can interact with but not vice versa, keeping your primary devices secure from possible insecure smart devices, but keeping everything manageable from the phone apps without having to switch networks. If not Google's way I'm sure the Eero engineers can figure out something that keeps the general functionality and security of Google's implantation of this idea.
I see this is still "under consideration" and I'm just hoping it gets approval.
-
Time for me to add again... since my first reply about 8 months ago, I have added another 30 devices in my home. From Alexa's, to smart switches, to montiors, to additional cameras.
I am now officially using over 130 IP address, on a daily basis in our house.
Yes I am not the norm, for a home use... but none the less....
I simply do NOT want to have to spend another 500-600 to add another mesh-network for the home automation devices, vs the other devices. If this isn't technically feasible with the eero hardware that we have today, just tell us. and be up-front about it. eero is a FANTASTIC product, but I can't any longer favor telling people to spend the high cost on it... if I know they are using numerous devices.
Even an AVERAGE house today, would benefit from two SSID's, or an ability to split to two subnets using the same SSID. -
I was a little disappointed to see this wasn't already a feature. With all the thermostats, garage door openers, energy bridges and the like showing up on my network these days, it would be great to be able to segregate them and control the connections from inside as well as external connections to these devices.
-
Another request for this capability. Please help us manage our home networks better.
-
This is my number one request for my eero network.
-
If i understand correctly, the Guest devices are unable to talk to each other. They can only talk to the internet. So why would you need multiples??
-
tibble This is talking about muliple non-guest networks. Or multiple primary networks.
For example:
Network 1 - For main owner network
Network 2 - For trusted guests to control smart devices (TVs, speakers, appliances, lights, etc...)
Network 3 - For non-trusted devices (Eero guest network). Bought a $10 cheap smart device and worries it spies on your network? Have guests over but don't trust them to control your TVs? this is a perfect fit.
-
-
The ask is to have at least 1 if not more then one, additional "non-guest" SSID. You are correct, devices on Guest are isolated. So it really is only good for guests, to give them some internet access.
The need for this is seriously growing here in my house.... since my original post.... I have added almost 40 more IOT devices to my house, and now with wired-smart switches supporting 3-way light switching... I am posed to replace 100% of my homes light switches with smart-switches (which will be about another 15-20). When done, I will be north of 150 IPs used in my home, on a regular basis. Not even including tablets, laptops, phones that are not on all the time.
Conservative guess... I want to move 75 of them to a separate SSID, and subnet... but I don't want to spend another $800 on another wifi mesh network to support that (basically having two hubs everywhere, because I have the devices all over the house).
I am even okay, if I have to purchase an adapter or something to add to my eero V1, to give me the two subnets connections or SSIDs... I just don't want to replace, the eero which is working fantastic.
But if a solution doesn't arrive by early next year, I am going to have to look at going with some of the other competing mesh networks, and recoup my loss on the eero hardware.-
ebonovic I guess I still don't understand the why. I have all my not-trusted devices on the guest network so they can only talk to the internet. If i don't trust them, why would i have them on any network that they could talk to each other?
-
tony@thedisarros.com
Because most of the IOT devices, perform much better on the TRUSTED network.
NEST devices; so I can access them via the app on phone, while in home... isn't delayed going out over the internet (and in the case of the NEST Protect, you can't respond and silence alarms in that mode)
Light Switches; Cameras, Etc...
Also in a case like myself, I don't benefit from Guest SSID in the same manner, because my eero is in BRDIGE mode, because I use a separate router for the home. EERO doesn't do my NAT for my network. -
A great example of this need is a Rachio sprinkler controller. It requires the configuring device to be on the same WLAN as the Rachio controller itself. Thus, it's impossible to configure it to reside on the guest WLAN which only has internet connectivity. Creating multiple non-guest WLANs allows this style of configuration but preserves IoT vs. non-IoT through network segmentation.
-
uury a more advanced solution to that would be the ability to specify certain guest devices that can talk to each other. Basically a single SSID for guest(so to not waste airtime) but different subnets for the different groupings.
Create group-> Which Devices-> allow communication with each other yes/no
-
tibble Yah, but I think that is really getting advanced for home users, the targeted audiences for these particular mesh networks. I think TWO SSIDs and a GUEST one, is about as far as it should go.
Getting it some serious advanced routing and permission on there, could cause issues as updates and advancements come down the pipe..... Ubiquit and CISCO based items I believe can do that today, but you are paying an even higher penny on those. -
ebonovic the fewer SSIDs the better in my opinion. Once WPA3 is out with even better forward secrecy key agreement I think a single SSID would be the best bet. I have very very few things that need to communicate with each other, most are internet only
-
tibble In that context, how are you going to address large numbers of necessary IP addresses.
Right now, I have gone past 125 in the home network. When I complete changing all the switches over in the home, I will be well over 150. I am getting close to the limits of IPv4, and we all know IPv6 isn't really ready yet for in-home usage yet, most of the devices will need to be swapped out....
Goal isn't just having two SSID's, but to allow that 2nd SSID to be on a separate subnet.
But if we can't get that, having a separate SSID for home automation devices, where I can have a crazy complicated and secure password for it, works... because I wouldn't really ever have to share it with anyone... just myself. thus not the horrible experience of having to re-add them (took me days when I added my eero)In my home, anything that can be hard-wired is. But more and more IOT devices (Even those that are not mobile) are going WiFi only
-
ebonovic IPv4 can handle plenty of addresses. The 10.0.0.0/8 network has over 16 million ips. Beyond that, you can have seperate subnets but the same SSID. The group feature could have a different addressing scheme for each group. Again, fairly complicated to implement but would be sweeeeeeeet.
-
-
tibble Many of us are just looking for a more secure way to have many IoT devices. However Eero chooses to implement this idea securely we'd be fine with, whether it be more SSIDs, or a designation of a device in the app that applies special rules to it, or if it handles it like the OP mentioned Google WiFi does, with a second SSID that can be accessed from the main SSID but not vice versa.
This is not something that would be forced upon any user so I don't understand the opposition.
I gave an example before, but many smart devices, which still function well but are no longer actively supported by their developers, end up with unpatched security issues as new exploits are discovered. These devices shouldn't be on your main network to keep your computers safe, but they still function so they don't need to be replaced (and many times I'm sure people aren't even aware of what devices could pose a security risk). Sure, some of those devices can function well on a Guest network if all they require is Internet access to function, but if they require/include interaction with an app, sometimes the app and device need to be on the same network.
We're just looking for some sort of solution to that scenario, however Eero would like to do it.
-
essential No strong opposition, just trying to find the most elegant solution. SSIDs take up a significant amount of airtime. Thankfully i'm in a house with few neighbors, but for apartment buildings,etc, it's always nice to be a good citizen.
-
-
+1
Additional SSID beyond Guest Network would be great to support Home/Guest/IoT Network devices
-
+1
I was hoping this would have been added by now but with how long this has been requested I'm starting to wonder if I need to find another solution to get this capability.
-
pchaves oh 😢
I just joined eero. Is this how the support has been? 24months if backlog “under consideration” features?
-
Emily yes. They make sure features are fully baked before releasing. They have a very good beta test process and tend to be good about keeping things under wraps so people don’t rush them to release too early.
-
-
This would be amazing!
And bypass the need for this feature: https://community.eero.com/t/y7g40n/allow-airplay-apple-tv-chromecast-control-on-guest-networks
Eero, has there been any talks to implement this? What is an estimated implementation time?
