Sponsored Links

Anyone on Giganet?

IPv6 also didn't work for me failing with status-code NoPrefixAvail on my Ubiquiti Edgerouter. I opened a support case. They reset something their end & it started working. Unfortunately, I rebooted my router a few weeks later and now it's stopped again. Would love to know why
 
Sponsored Links
It's rather frustrating. I do use IPv6 (and work in sw). It needs to work reliably. I had specifically asked if they support ipv6 before switching.
I'm hoping there's more than a one-off fix to freeing up a stuck allocation - this should work reliably on every connect, especially with the router they provide.
Hopefully we can work through this, as other aspects of the connection are fine. But I've been using ipv6 rock solid on zen for a few years. It's definitely possible.
If they can't solve ipv6 I'll likely need to leave but I hope it doesn't come to that.
One reason I opted to start using the offered eero is to get support/ensure the basics are working. Otherwise it's quite a disappointing wifi system (albeit I only have one unit). So limited. The auto band switching seems far worse than a fritz mesh I had previously - seems to prefer 2.4 Ghz far more cutting down some locations 300 Mps -> 70 Mbps, though the peak speeds closeby are better (wifi 6 vs wifi 5). Zero insight into logs etc. But so be it. I have choices, and it was interesting to try.
 
Did some playing around today and found that if I turned off "rapid commit", the prefix delegation succeeds!
 
I could try the fritzbox again, but mostly I'm trying out the Eero - in part as this should work perfectly with Giganet as their supplied router!
Contacted them around 1530 on Friday - no technical update yet. Rather friustrating.
(Aside: oddly formatting/new lines don't seem to work here.... ?!)
 
@IanCass A few times when testing at the weekend I thought I'd figured the cause, but when I tried to repeat it seemed as if the problem was more intermittent, or based on a timeout rather than any settings I changed
(The Eero is so dumb-user oriented that the best it has is IPv6 on/off !)
 
Well, I turned IPv6 back on whilst running tcpdump & I could see the dhcp6 solicit & a reply with status-code NoPrefixAvail just like it has been every other time I've tried it. I then turned "rapid commit" off and it sprang into life. I suppose it's possible it was a coincidence but would be unlikely.
 
Sponsored Links
Hmm. Well I know the fritzbox supports that setting, so I may well try
- reboot the Eero to see if it works
- Try the fritz (default settings)
- enable rapid commit
- try eero again
Any info helps me, and may help giganet get to the bottom of it (unless it's just a known config issue that can be fixed as a one-off)
 
Back from some testing.
  • whether rapid commit was on or off, no ipv6 prefix allocated on the fritz 7530 via the giganet connection (and ipv6 test sites all fail)
  • whether rapid commit was on or off, a ipv6 prefix WAS allocated on the about-to-be-terminated zen connection (test sites pass)
  • the eero continues to get no ipv6 connection on giganet
  • I must have reconnected ~6-8 times to each of zen and giganet via fritz - behaviour was consistent, and another 2 times on the eero back with giganet only
I can only assume the issue is at their end. I've lost track of how many connection attempts since Friday, almost entirely failing (except once on Sunday, and I think initially on Friday)
not done any wireshark sniffing yet - will have to move a tied down switch to tap into the wan
 
I noticed an interesting note at https://openwrt.org/docs/guide-user/network/wan/isp-configurations

DHCPv6 is used to IPv6 prefix delegation, but the IPv6 prefix must be released by the router before the prefix will be issued again to either the same router or to another router. If this doesn't happen, an error of NoPrefixAvail during DHCPv6 negotiation, and odhcpd will complain that there is a local route, but no prefix, so it doesn't issue IPv6 addresses to LAN clients.
I am pretty sure what I am seeing, which begs the questions:
* does the eero correctly release the prefix in normal operation
* what is the mechanism to get working again if, for example, the router is simply power cycled (power failure, or by human). Is there a timeout? Is it too long
 
I have a theory.

When I connected my Eero, it worked fine. When I connected my Ubiquity Edgerouter, it couldn't get an ipv6 PD. I contacted them and they reset it, and I could get a PD on my Ubiquity. Some time later, it stopped working. Turn off "rapid commit" and it starts working.

I think the PD delegation is relating to the DUID (https://en.wikipedia.org/wiki/DHCPv6) but for me, the renewal didn't happen because they don't support "rapid commit" that's two message exchange vs 4 message exchange here https://support.huawei.com/enterprise/en/doc/EDOC1100008282/42f555dd/understanding-dhcpv6
 
I'm still persuing with them.

* They allocated me a new prefix. This worked. Once! Then as soon as I'd rebooted the eero, no ipv6 prefix allocated
* They cleared out leases. This worked. Once! ... then no more
So it seems as if an action to 2nd/3rd line gets it to work once. I think more is needed.... ;-)

This is actually quite worrying. I expect/need ipv6 to work. They said they support ipv6. This is not sustainable. But we'll hopefully work together to get a fix. If not, it may be a case of changing ISP, but it would be unfortunate.
 
Sponsored Links
I'm still persuing with them.

* They allocated me a new prefix. This worked. Once! Then as soon as I'd rebooted the eero, no ipv6 prefix allocated
* They cleared out leases. This worked. Once! ... then no more
So it seems as if an action to 2nd/3rd line gets it to work once. I think more is needed.... ;-)

This is actually quite worrying. I expect/need ipv6 to work. They said they support ipv6. This is not sustainable. But we'll hopefully work together to get a fix. If not, it may be a case of changing ISP, but it would be unfortunate.

How strange. I would understand it if you were trying to get your own router to work, but you'd expect the supplied Eero to work first time, every time!
 
I'm now thinking the probem could be that the DUID is not stable across reboots.
The default (type 1) DUID is DUID-LLT - so it's a mac address (link layer) + time. The router would be expected to generate and then save this value to be persistent across reboots/reconnects (not sure about reset)
Alternatively a type 3 is DUID-LL which is a fixed value + mac address - this will effectively be fixed.
What if the eero is using type 1 and failing to persist the generated value. it would then be different each time, meaning that the prefix allocation will fail, as it will likely still be reserved by the previous duid (there may be a timeout, plus router may explicitly release at the end of a session)
 
Whatever the Eero is doing, you'd expect it to be working.

If it helps, I accidentally rebooted my Edgerouter Lite a short while ago and when it came back up, IPv6 is working perfectly.
 
Draytek 2925, multiple reconnections and no change to IPV6 which works as required. When setting it up to get IPV6 to work I had to select 'Connection type PPP' other IPV6 connection types did not work.
 
It's been a frustrating week and a half. I've escalated the problem, but I think I've found a stable configuration.

Fritz 7530 with rapid commit disabled - seems to get a prefix reliably

* fritz with rapid commit on - flaky. worked a few times, then kept getting prefix not available. This worked fine on zen...
* eero - usually works first time after new allocation/lease free, but not always. maybe 2nd or 3rd. Then once only. Ever. Maybe it has a bug with the DUID *and* always uses rapid commit? !
 
Sponsored Links
Update - ISP reported, eero identified fix, probably out late March.
Of course in the meantime the FritzBox has been working flawlessly as a router, and also has better firewall, monitoring, supports 1500 MTU for pppoe etc… so I may now stick with it (though I do plan to test the eero for completeness!)
 
Update - ISP reported, eero identified fix, probably out late March.
Of course in the meantime the FritzBox has been working flawlessly as a router, and also has better firewall, monitoring, supports 1500 MTU for pppoe etc… so I may now stick with it (though I do plan to test the eero for completeness!)

Excellent. I wonder if the fix will be to enable rapid-commit on ISP side or disable it on Eero side?
 
Excellent. I wonder if the fix will be to enable rapid-commit on ISP side or disable it on Eero side?
Unfortunately I don’t have the precise details. However I get the impression this is very much an eero software update.

The Fritz is flawless though I did need rapid commit disabled
 
Top
Cheap BIG ISPs for 100Mbps+
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Vodafone UK ISP Logo
Vodafone £24.00 - 26.00
150Mbps
Gift: None
NOW UK ISP Logo
NOW £24.00
100Mbps
Gift: None
Plusnet UK ISP Logo
Plusnet £25.99
145Mbps
Gift: £50 Reward Card
Large Availability | View All
Cheapest ISPs for 100Mbps+
Gigaclear UK ISP Logo
Gigaclear £17.00
200Mbps
Gift: None
Community Fibre UK ISP Logo
150Mbps
Gift: None
Virgin Media UK ISP Logo
Virgin Media £22.99
132Mbps
Gift: None
Hey! Broadband UK ISP Logo
150Mbps
Gift: None
Youfibre UK ISP Logo
Youfibre £23.99
150Mbps
Gift: None
Large Availability | View All
Sponsored Links
The Top 15 Category Tags
  1. FTTP (6024)
  2. BT (3638)
  3. Politics (2720)
  4. Business (2439)
  5. Openreach (2405)
  6. Building Digital UK (2330)
  7. Mobile Broadband (2143)
  8. FTTC (2083)
  9. Statistics (1899)
  10. 4G (1813)
  11. Virgin Media (1762)
  12. Ofcom Regulation (1582)
  13. Fibre Optic (1467)
  14. Wireless Internet (1462)
  15. 5G (1404)
Sponsored

Copyright © 1999 to Present - ISPreview.co.uk - All Rights Reserved - Terms  ,  Privacy and Cookie Policy  ,  Links  ,  Website Rules