62Feature 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:
https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption&tab=ipv6-adoption
For example I currently have Comcast at home with native IPv6 support. I will only buy products that support IPv6.
Bob
-
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
Hi Nick,
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.
Best regards,
Martin
"
-
Jeff,
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.
-
I'd say ipv6 support in the dhcp service would be a great (reasonable) start
-
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:
https://www.google.com/intl/en/ipv6/statistics.html
Similar number for Facebook, Netflix, etc.
Other mesh wifi solutions such as Google Wifi and Ubiquity AmpliFi now support IPv6.
Bob
-
Like rmh , I am very disappointed in the current lack of IPv6 support. This is hardly secret sauce, so I would hope that Eero could be slightly more transparent on their plans to 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.
-
So here we are a year later, and eero still doesn't support IPv6, and has not announced plans for IPv6 support. My four-year-old Apple AirPort Extreme does IPv6 perfectly (i.e. 20/20 on IPv6 tests). I've officially given up on eero.
-
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.
-
ChrisCJA90
i was in the “happy to have eero with IPv4 / wait IPv6 out camp” but I researched your Nest Protect issue and it is (a) true, and (b) annoying. I have Nest protects from an earlier era and that was not the case circa 2014 — IPv4 was fine. But I need to add new units to our house and this will cripple my system.
Count me out of the “wait it out” camp.
Eero, I join my fellow *owners* in simply wanting to know if and when we can expect to see IPv6 — in beta and in full deployment.
-
-
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
-
mike1234i
Thanks Mike - I believe you are right regarding the protects - I added another router that does support IPV6 here and still having an issue with adding my Protects to my account, so I may have another issue here.
Im expecting a Nest Secure Alarm system in the mail any day now and the reviews have all said that to use that product, IPV6 must be enabled on the router - Hopefully its the same case, otherwise I’ll be using the other router for those communications.
In the end though, it’s just disappointing Eero still has this “In consideraton”. I feel like Eero is a forward thinking company but here they are way behind the ball.
Hopefully they play catch up soon as I feel like this is going to start becoming a bigger issue.
-
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 support@eero.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.
-
Jeff C. — I believe (a) it will be hard to simultaneously market eero as a premium product if it doesn’t work with mainstream products from, ahem, Google; (b) this appears to be a new requirement from Nest, as Protect didn’t previously require IPv6. But there it is, clearly in their documentation.
Please have a look at: https://nest.com/support/article/Recommended-Wi-Fi-router-and-access-point-settings-for-use-with-Nest-products
quote:
- If you’re trying to connect a Nest Protect, make sure your router supports IPv6. Your Nest Protect uses an IPv6 address to communicate and set up connections with other Nest Protects.
Note: Even if your router supports IPv6, your internet service provider may not. Contact your provider to make sure that IPv6 is supported in your area. If your provider doesn’t support IPv6, you will not be able to add your Nest Protect to your Nest Account. This means your Nest Protect will not send alerts to your phone or tablet, but your Nest Protect will still be able to detect smoke or CO and sound an alarm.
-
tc60045 —
Thanks for following up.
As mentioned, the 2nd-generation Nest Protect (as well as the new Nest Secure) works on eero networks. I can't speak to the Nest documentation, however, I can assure you that we haven't seen any consistent reports from customers saying they are unable to get their Nest Protect to work on their eero networks.
-
-
Stop writing excuses so that you may ignore these reasonable requests and writing them off. Provide an update to allow for a modern IPv6 technology to be used. It doesn't take a rocket scientist to add in this type of stuff.
-
derekcentrico —
No excuses being made and I can assure you we are not ignoring the request for IPv6.
However, we don’t want anyone being misinformed when it comes to the products that are compatible with eero so we are just ensuring that the correct information is shared from our end.
As mentioned, we’re actively working on bringing IPv6 support to eero. I wish I had more to share, but at this time, I don’t have any more information than what has been previously stated.
-
Jeff C. "trust us, we're working on it " for over a year strains credulity. This is a big, and now embarrassing gap in eero's value prop.
Headline: "Home networking darling eero falls behind: can't support latest products from Nest, others." You can argue that isn't right, but good luck arguing with a tech journalist.
How does eero get out of this? (a) start coding and (b) get public. Public beta - start enrolling. Milestones, start committing, even if that is waterfally and not Agile. You can't afford to lose the affinity of your customers, so enroll every last complainer starting now. You'll be better off. Now get coding!
-
-
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.
-
rcrcr - same. Replaced them, though I still have them physically in place in the event eero rallies and solves the macbook pro issues.
-
-
Hello,
Would it be possible for Eero to provide any update on IPV6 support?
The lack of comments are as concerning as the lack of actual support.
regards
-
Hi,
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.
-
So very glad I checked in here first. So sad that such a fine product is stuck in the stone ages when it comes to IPv6 availability. Very important in my line of work. Adapt or die. Your competitor got my money. Wake up EERO!!!!
-
I just found out my ISP is implementing IPv6. I really would like to keep my brand now gen2 Eero system. Sooooooo where is my IPv6 support?!
-
The workable approach I’ve taken is to continue using the ISP-provider router, which supports IPv6, and place the Eeros in bridge mode. This supports IPv6 on my home network. Workable.
-
-
Hi everyone —
The status of this feature request has been upgraded to Planned.
Stay tuned 🙂
-
Jeff C. does planned mean weeks or months away? :)
-
kodyaten at this time, I'm unable to provide any additional details. However, as mentioned, stay tuned. Thanks for your ongoing interest and support!
-
Jeff C. Translation, do not hold your breath.
kodyaten Would definitely expect months not weeks. If it was weeks they would be more definitive. After following this thread and a few others the status change probably means they are either beginning to work on it or that it was approved as part of the internal roadmap.
-
-
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.
-
Jeff C. I am very pleased to see that eero has released official support for IPv6.
In fact, I have been running the IPv6 beta version since early this year. I have IPv6 from Comcast and it has worked reliably with out any problems since I first installed it. I am very pleased how well it works.
Thanks!!!!
-
Jeff C. That's great news. Thanks Jeff! Too bad I couldn't use my Eero network and had to send them back. I'm ready to jump back onboard. Any way to get my original discount back?
-
Jeff C. Thank you to the eero team for listening and implementing IPV6. Look forward to turning it on.
-
Jeff C. Fantastic work to you and the eero team! It was only eight days ago that we suspected that this would be weeks (or months) away... and here we are with a bona fide release. The rapid response is very much appreciated, even after a very long information drought. Kudos! 😸
Also, thank all of you folks on here for voicing your wants/needs for IPv6 👍
-
Jeff C. This is great news. However, it appears that if you use Eero plus features, the DNS servers used do not support IPv6. This limits the functionality since the is no IPv6 name resolution. Does this need to be reported to the development team?
-
Jeff C. I'm a Eero plus user as well - interested to hear more about this issue w/DNS servers.
-
Just went to an IPV6 test site ( http://test-ipv6.com/ ), and received this result:
Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites. [more info]
-
Danabw When I run the test, I get 10/10. I am not seeing an eero DNS problem. See attached.
-
Jeff C. You were so pumped to write this on this thread weren't you? :)
-
rmh Are you an Eero Plus user? This issue appears to be seen (so far) when Eero Plus is enabled.
-
Danabw I am not using Eero Plus.
-
rmh Thanks for confirming that you are not using Eero Plus. Eero Plus uses different DNS servers that don't appear to support IPV6.
-
Jeff C. Good idea to confirm w/your Dev and QA teams that their testing includes Eero Plus and any other add-on/fee based services you offer.
-
Hi everyone — thanks for chiming in and for your questions regarding using IPv6 with eero Plus. Before getting into more details, I wanted to make one thing clear. With eero Plus enabled, you're still able to communicate to the IPv6 Internet. However, because of how eero Plus works, DNS requests are intercepted on your gateway eero and passed to our DNS service. For that reason, we've seen issues with the tests from test-ipv6.com , however, if you try going to ipv6.google.com or searching what is your IP, you will see that IPv6 is indeed working.
For those who want to take things a step further, you can go into your computer's terminal and do a "dig AAAA google.com" which will also display the IPv6 address that the site is connecting to.
In all cases, DNS lookups of a domain name do return the IPv6 AAAA record and all subsequent communications do go over the IPv6 internet (assuming available from your provider). The DNS lookup step of a request is unique in the eero Plus case.
-
Jeff C. Thanks for clarifying the info here, Jeff, very helpful. And thanks for helping to make this happen.
-
Jeff C. I'm not getting those results. When I browse to https://ipv6.google.com/, I get
This site can’t be reached
ipv6.google.com ’s server IP address could not be found.
- Try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
I have restarted my network gear and my computers. I have also tried this from several systems with similar results.
One item to note is that my eero is not configuring an IPv6 DNS server, but I am getting IPv6 network adapter addresses.
DNS Servers . . . . . . . . . . . : 192.168.1.254
-
mike1234i Sorry for the delay! After speaking with some of our engineers, they noted that this seems like there is another upstream router put in front of your eeros. Is that the case in your network?
-
Jeff C. I am using Uverse. They only offer routers, not modems — so by definition they route traffic. However, I am passing the public IP though to the eero, so the eero received the public DHCP IP address directly from my ISP.
-
Jeff C. I feel bad for not figuring this out sooner. I use a Circle web filter for my kids and I forgot that I left it on for me. Circle operates by intercepting DNS requests and it was obviously interfering with the v6 responses. After disabling my filtering all IPv6 sites are working great. Sorry to sidetrack this discussion. Hopefully someone can learn from my mistake.
-
mike1234i —
Ah! Definitely an edge case I didn’t think of. Glad you were able to get it all figured out.
-
Jeff C. Yay! ... now onto the missing features.
IPv6 incoming connections are blocked (a safe default) with no way to open ports in the firewall for them (bad). It kinda defeats the purpose of IPv6 if you can't allow inbound connections when you _want_ them.
That appears to be tracked in https://community.eero.com/t/63rn4v/allow-ipv6-machines-to-accept-incoming-connections
-
Jeff C.
Installed my new Eero today and I can say your IPv6 support is lacking at best. You only offer an on/off switch with an expectation of DHCPv6.
I realize that static IPv6 isn't exactly a common configuration, but you can't say you support IPv6 if you only support specific configuration. I can't even find a way to spin up my own DHCPv6 server and point the eero at it.
I wasn't impressed with support, who tried explaining to me that my IPv6 autoconfig address (fe80::) was my WAN address.
-
-
Wow! eero finally delivered the goods.....
will wait for this weekend to re-setup the entire Comcast based rig. Everything is in bridge mode currently.....
-
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.
Mark
-
Thanks for the implementation!
-
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.
