802.1Q VLAN Trunking
In addition to the ability to add multiple SSIDs and assign VLANs to each, 802.1Q trunking for these vlans would be required to allow the EERO to tag traffic that is being sent out.
-
Its been three years, you really think they will implement this? The target market is not us or anyone who actually cares enough to learn about proper networking. Eero is the Apple of WiFi, and I dont mean that in a positive way. Plug it in, trust us, its magic. Somehow modifying DNS is an advanced feature, what a joke.
-
I have loved the performance and stability of my Eero’s, but the lack of company response on this topic (SSIDs, VLANs and VLAN trunking) has been really disappointing. I unfortunately will have to dismantle this reliable (5 eero) WLAN and migrate to Ubiquiti or some other option with mature security features.
-
I’m a new eero pro user, and so far the performance and reliability are much better than my Linksys Velop mesh. I really want to leverage this with my IoT segregation using a managed switch with 802.1Q and pfSense. I’m going to have to set the Velop back up as dedicated IoT mesh and segregate there. Quite ridiculous.
Someone, please, please, please... give an official update. Even unofficial would be good.
-
+1 from me. Any news on this? Request was first made three years ago. Is the hardware on the Eero actually capable of supporting VLANs with just a firmware update? Some kind of definite answer would be appreciated or I might need to (very reluctantly) sell my Eeros and move to a different AP, Ubiquiti maybe. Much rather stick with Eeros as I now have 6 units. Can someone please at least give an update?
-
This is from one of the developers:
- https://www.reddit.com/r/eero/comments/jmq4ka/will_all_preorders_through_eerocom_ship_today/gaz4a5j/
My semi-informed guess: it's not happening anytime soon. I'm just going to setup a new IoT WiFi Mesh with my old Generation 2 Pro nodes, then do the trunking of all that traffic when it hits the physical port of my managed switch.