Feature request: eero needs to support IPv6
eero is way behind. Google is seeing about 15% of their traffic being IPv6 and the adoption in the US is about 30%. See:
For example I currently have Comcast at home with native IPv6 support. I will only buy products that support IPv6.
My 3 pack Google Wifi arrived two weeks ago and it took roughly 5 minutes to replace the eeros. The setup experience was slightly faster, since I just needed to scan the QR code on the back of the devices.
After applying the latest firmware and enabling IPv6, everything is running smoothly and performance/coverage seems on par with the eeros.
Even though I love supporting the "small company", I now regret not saving $100 on the 3 devices and getting a working IPv6 setup right away.
For anyone hoping eero take their customer feedback seriously, below is a LinkedIn message I sent to Nick Weaver (CEO of eero) on June 29. He hasn't responded so far.
eero and IPv6
First of all congratulations on your latest hardware launch and creating a great product. Most user friendly router/wifi experience I have had so far. :-)
While I think it is great that you are improving the hardware and offering a new security package, I am saddened something very fundamental is missing with no update or clear communication in sight: IPv6 support.
I'd like to draw your attention to the following community thread: https://community.eero.com/t/q5m604/feature-request-eero-needs-to-support-ipv6
I think it would be very helpful with some clear communication from a company executive on this matter, not just for current customers but I imagine it will also affect customer decisions on which vendor to use.
Can Eero at least say it is planning to implement IPv6 in 2017? I work for a top 200 website (based on Alexa rankings) and we are seeing more and more IPv6 every day. Being mostly US based, we are seeing nearly 30% of our traffic coming in via IPv6 so far in 2017. With the IPv4 shortage, this is only going to keep increasing. I just really hope that I can get rid of my double NAT setup in 2017!
As with everyone else, I was extremely surprised to find out that the a company that is trying to revolutionize home WiFi and become the operating system of the home wouldn't have IPv6 support on day one for the product launch. Not having it by the time the 2nd generation platform was launched makes it clear that this is not a priority for eero. Time to return and replace.
So, I guess this makes my mind up. My son has been hounding me about his Xbox not signing in. We have been fighting WiFi problems in our house moving from AP to AP and hoped EERO could fix it soon! It’s been a month or so and no closer to a fix. Anyway, back to the Xbox. So, when you try to sign in it will continuously boot you out. I noticed the EERO was listed as connected but not supporting IPv6. I connected to my iPhone, which does support both versions, and voila! Connected right away. Then I signed out and back in to the home connected EERO and everything seems to be working. Not sure if this is an IPv4 or v6 problem but it was definitely related to the EERO’s
I assumed Eero supported IPv6 when I purchases 3 Eros boxes a month ago so am pretty surprised and disappointed. IPv6 has been in the open source code bases for years so it's insane that it's not supported in this product.
Thinking of a workaround..... my xfinity router supports IPv6 and it looks like the Eeros boxes could be placed in bridged mode. That might work, but does sound like it kills the handy management features for the Eeros boxes.
It's been over a year since I raised this issue. Sill no firm plan for IPv6 from eero.
In the mean time Google is now seeing over 21% of their total access as IPv6. See:
Similar number for Facebook, Netflix, etc.
Other mesh wifi solutions such as Google Wifi and Ubiquity AmpliFi now support IPv6.
I have a specific reason why your customers are going to want/need IPV6 support.
Windows has well-known issues with network printer discovery, which results in a lot of unhappy customers with "printer off-line" issues when trying to print from Windows. The printer is really online, Windows just can't see/find it. Just ask my family (who look to me for level 1 tech support), or search online for "Windows 10 printer offline" issues.
We have a couple HP inkjet printers that have had this issue, and when I spoke w/HP support about it they said that a key strategy they are spinning aggressively for their customers' with this issue is to move their printer to an IPV6 port connection to the computer. This apparently resolves the "lost/offline" printer problems for most users.
It sounds like Eero's lack of support for IPV6 could block Eero customers from using this approach to get around Windows 10 printer discovery issues. Is that correct? HP must own 50 to 60 percent of the consumer printer market, that sounds like a lot of folks who might be negatively affected.
Wow - Created an account here just to add my opinion on this topic. I'm shocked that Eero - My $600 (CDN) WiFi solution doesn't support IPV6. Tried to add my Nest Protect Smoke Detectors to the network today and found out that they require IPV6 to add to your account. With my current setup, I'd prefer not to simply use Eero in bridge mode to take IPV6 from my provider's basic modem, so it looks like I'm going to have to add a clunky $50 WiFi access point to my network simply to provide network connectivity to my Nest Protects.
This is a feature that has been around for quite some time, and for the price and quality of the Eero units (And the $125/year that I pay for Eero Plus), I would expect Eero to stay on top of the times.
Please add this feature ASAP or at least give us insight into your roadmap. Very disappointed and this on its own will cause me to not recommend Eero to people I know - Unfortunate given that my experience otherwise has been very positive.
First, I agree with the calls to support IPv6. I suspect that the in the very near future IPv6 will become a necessity -- At that point, Eero users will need to decide if they should replace their systems or be relegated to second-class citizens.
Regarding the Nest Protect, I have several Protects and they work on my Eero WiFi. It seems that IPv6 is required for LAN communications. Eero routes IPv6 traffic on the LAN, but does not have a v6 DHCP server nor will it route that traffic to the Internet.
Even if your router is not on this list, you may be using a router that is incompatible with Nest Products. The list of symptoms below can help you to identify routers that may be incompatible or are using incompatible settings.
Some routers support IPv6 for external internet connections but do not support IPv6 communications over the local network, which Nest Protect requires.
Using the Nest Protect with incompatible Wi-Fi routers/access points may result in:
- Difficulty adding a Nest Protect to your Nest Account
- Nest Protect offline in the Nest app
Hi mike1234i / tc60045 / ChrisCJA90 —
Thanks for checking in and for the discussion around Nest devices (specifically the Protect and Secure) on eero networks.
Both these products (including the recent Protects) work perfectly fine on eero networks without IPv6 being enabled (here is a user saying such on the Nest subreddit regarding the Secure). If you run into any trouble, please don't hesitate to reach out. Our support team will be happy to help. You can always give us a call at 1-877-659-2347 or email us at email@example.com .
As for IPv6 support, as it has been mentioned here in the past, it is something we believe in and are actively working on. As soon as we have an update, this will be one of the first places to know.
I am very disappointed to find out that my "high end" mesh wireless system I purchased just long enough ago to not be returnable does not support IPv6.
My work occasionally requires me to access IPv6 devices remotely from my home and when that need arouse recently I discovered I no longer had IPv6. Shame on me for not testing it right away but I would not have even guessed that after paying that much money for the system that this feature would be missing. Yours is the most expensive system on the shelves at BestBuy and the only one that does not support this protocol. Again shame on me for not checking...
I will no longer be recommending this system to customers, clients, family and friends. Sort of feel ripped off.
Judging by your inability to say anything further, this is way down the priority list and has been since the issue was first raised.
Glad I was able to stop a couple of my team mates for purchasing systems for their homes. Hopefully I can sell my system to recover some of the costs.
I am in in the same boat, @mclift. I have retired my own personal units (of which there were several), and am no longer recommending. In larger part, for me, this was due to other issues (see: https://community.eero.com/t/36l3gk/problems-connecting-macbook-after-update) but the ongoing lack of WAN-routed IPv6 was also a significant factor in that decision.
I just installed eero for my in-laws and found that Spectrum is providing only IPv6 addresses. My workaround for this issue was to install a Dlink Cloud router (even the cheapest routers provide IPv6 support) to the Arris cable modem and then connect the eero to the Dlink. The Dlink router will communicate with Spectrum's network's IPv6 and then will talk to the eero via IPv4. This works great and performance is excellent.
I am disappointed to have to install intermediate hardware to make this work, but the result of having great WiFi throughout the house is worth it. IPv6 adoption is increasing at a fast rate and it is important to support this.
I feel it is important to let prospective customers know that they should check their network for IP version before ordering the product.
Hi everyone —
Exciting news, IPv6ers!
IPv6 is now available for all eero networks. To enable IPv6, you will need to be running a minimum of both eeroOS version 3.7 and eero app version 2.14.
I also just want to take a moment to thank everyone for sharing your interest in this feature, as well as for your patience.
For more information, please see this help center article.
Well I was days away from purchasing my next system due to a large project that would require me to have IPv6 access from my home office so this is welcome news. I know I could have gotten another router and done bridge mode but the whole point of purchasing the eeros was not to have to think about my home wireless and now it is back to just working 🙂👍
Happy to report that IPv6 is activated and working like a charm. eero is back on my recommended for home list.
With IPv4, NAT and port forwarding allowed me to access devices on my internal network from the internet. With eero's IPv6 enabled, the access to these devices is no longer possible, apparently. After contacting eero support I was told that eero's current implementation of IPv6 does not have provisions for this kind of pinhole functionality. So...
1. erro, please consider this a feature request, so we can use the IPv6 address space to access devices on our internal network from the global network.
2. For anyone who may have previously setup IPv4 NAT and port forwarding, be aware that you'll have issues attempting this same functionality using IPv6.