Moved from VDSL to Fibre, IPv6 gone AWOL

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Moved from VDSL to Fibre, IPv6 gone AWOL

darthmeow

101 posts

Master Geek

#230792 13-Mar-2018 13:55

Good afternoon all.

Have just moved to "near gigabit" fibre with 2Degrees off VDSL (following a nightmare saga involving Chorus and the ROW flip-flop), but for some unknown reason IPv6 refuses to work. I've got a ticket open with the support desk but it seems to be going nowhere, so here we are. Using the Fritz 7490, have tried the following:

Factory Reset to defaults - no love
Manually assigning the static prefix (yes paying for static V4 and V6 addresses) - systems get IPv6 addresses but no traffic wishes to pass.
A completely different router (dug an old linksys e3200 out of storage, flashed with advancedtomato, no love with v6 - also cannot handle above 130mbps!)

I have a funny feeling this /might/ be MTU related but after some poking around in the Fritz it looks to be OK and I can't really find a setting to force the MTU size. One would assume it'd just sort itself out. Also looking in the Fritz logs, I can see a lot of "Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL)." errors coming up. Been well over a week now since I lodged the problem and really curious to see if this has happened to anybody else. On the flipside other than this everything is running great! Wanting to get this sorted before I move everything over to a Mikrotik or Ubiquiti unit for a little extra nerd appeal in the network cupboard!

1 | 2 | 3 | 4 | 5

2320 posts

Uber Geek

Trusted

Lifetime subscriber

#1974166 13-Mar-2018 18:54

To quote @fe31nz from this thread (there is more MTU info in the original post):

fe31nz: ...

1) If your Internet connection is appropriately overprovisioned as fibre connections via Chorus are, then there is bandwidth available so that you can connect the Ethernet and VLAN 10 connections to the ONT using an MTU setting of 1508 bytes, and the PPPoE connection with an MTU of 1500 bytes. This requires also that the ISP router you are connecting to has up-to-date PPPoE server software that supports PPPoE connections with MTU 1500. As far as I know, all the 2degrees border routers will do this now. It also requires that your router has an up-to-date PPPoE client that supports MTU 1500 connections. Quite a lot of routers do support this, including Edgerouters, and almost certainly all other Ubiquiti routers. However, you have to manually set up the MTU settings to make it happen. To see if the connection is overprovisioned and has the later version of PPPoE software, the only way I know to find out for sure is try it out using the MTU 1508/MTU 1500 settings. If the PPPoE fails to connect after that, or no traffic (even IPv4) passes through it, then the connection in not capable of doing MTU 1508 and you will need to use the other solution below. Do not forget to add an MTU 1500 setting to the PPPoE settings - PPPoE connections default to MTU 1492, and will not be set to MTU 1500 simply because you have set the Ethernet port and VLAN 10 to use MTU 1508.

The FritzBox routers provided by 2degrees, with the 2degrees version of the FritzOS software installed, go one step further and will automatically try to connect a PPPoE connection at MTU 1500, and fall back to MTU 1492 only if that does not work. So there is nothing you need to do with such a FritzBox to make IPv6 work correctly. Other routers may do this as well, if you are lucky. But there is nothing about the Ubiquiti USG routers that leads me to believe that they will do this automatic fix - my bet is that they will need manual configuration.

...

Please keep this GZ community vibrant by contributing in a constructive & respectful manner.

2degreesCare

1537 posts

Uber Geek

Trusted

2degrees

#1974314 13-Mar-2018 23:00

Hi @darthmeow,

Could you please PM us your customer number/username so we can investigate? This has been popping up recently with a few customers, so we'd like to gather examples to spot the pattern.

Cheers,
^BRM

fe31nz

1229 posts

Uber Geek

#1974324 13-Mar-2018 23:51

A 7490 with recent firmware and automatically set up from 2degrees should just work. First, check the System / Update menu (I have a 7390, so it could be in a slightly different place) and make sure that the firmware is able to do its update checks and is up to date. Then check the System / Event Log page and see if you are getting regular "The service provider successfully transmitted settings to this device" messages. They should be happening about every 22 hours. If those messages are there, then 2degrees is autmatically checking the settings on the FritzBox and updating them if anything at their end has been changed.

It is possible for you to change settings from the ones that are automatically set up, and if you get them wrong, you could cause problems. But 2degrees should be able to see that and tell you about it.

To get detailed information about exactly what is going wrong, you can get your FritzBox to capture all the traffic on its WAN port Ethernet connection to the ONT. You can then load that into Wireshark and look at all the packets, including all the PPPoE negotiation, and see exactly what is wrong - if you know enough about the protocols involved to understand it all. Or you can send 2degrees the capture file for them to look at. To do that, instead of logging into your FritzBox using the usual URL, add /support.lua on the end of the URL. That takes you to a special hidden support page with lots of extra features on it. Click on "Packet Traces" which takes you to another hidden page that has the packet capture options. I can never remember exactly which one you want, either "eth0" or "wan", so you might have to try them and see which one gives you packets with the PPPoE headers on the front. You do not want the "Internet" ones - I believe they are for when you are using the DSL interface.

When you click on those Start buttons, you will be asked where to save the data to a file. You should make sure that not much traffic is happening out to the Internet, as you will be capturing ALL the packets in both directions, and that can be too much to be sent back to your PC via only one direction of the Ethernet path from the FritzBox to the PC. And too much traffic will obscure what you are looking for. When you have it capturing, I think you can then unplug the FritzBox from the ONT, wait 10 seconds or so for it to disconnect (PPPoE takes a while to give up an existing connection), then plug it in again and capture the initial PPPoE negotiations. Then click on the Stop button and see what Wireshark can show you in the capture file.

Warning: If you have VOIP phone via the FritzBox, when you capture all the traffic, you will be recording any VOIP conversations happening at that time. If you are not a party to the phone call involved, that is illegal wiretapping and can get you a jail term. Make sure the phones are not being used! Including softphones! Wireshark makes it easy to just click on the VOIP traffic and play back the audio. The easy way to ensure no-one will be on the phone is to directly connect a laptop (or PC) to the FritzBox, unplug everything else on the LAN ports and the phone jack, and disable WiFi. Then do the capture from the laptop. That also minimises the amount of Internet traffic.

Wireshark is here:

https://www.wireshark.org

darthmeow

101 posts

Master Geek

#1974326 13-Mar-2018 23:58

fe31nz:

A 7490 with recent firmware and automatically set up from 2degrees should just work. First, check the System / Update menu (I have a 7390, so it could be in a slightly different place) and make sure that the firmware is able to do its update checks and is up to date. Then check the System / Event Log page and see if you are getting regular "The service provider successfully transmitted settings to this device" messages. They should be happening about every 22 hours. If those messages are there, then 2degrees is autmatically checking the settings on the FritzBox and updating them if anything at their end has been changed.

It is possible for you to change settings from the ones that are automatically set up, and if you get them wrong, you could cause problems. But 2degrees should be able to see that and tell you about it.

To get detailed information about exactly what is going wrong, you can get your FritzBox to capture all the traffic on its WAN port Ethernet connection to the ONT. You can then load that into Wireshark and look at all the packets, including all the PPPoE negotiation, and see exactly what is wrong - if you know enough about the protocols involved to understand it all. Or you can send 2degrees the capture file for them to look at. To do that, instead of logging into your FritzBox using the usual URL, add /support.lua on the end of the URL. That takes you to a special hidden support page with lots of extra features on it. Click on "Packet Traces" which takes you to another hidden page that has the packet capture options. I can never remember exactly which one you want, either "eth0" or "wan", so you might have to try them and see which one gives you packets with the PPPoE headers on the front. You do not want the "Internet" ones - I believe they are for when you are using the DSL interface.

When you click on those Start buttons, you will be asked where to save the data to a file. You should make sure that not much traffic is happening out to the Internet, as you will be capturing ALL the packets in both directions, and that can be too much to be sent back to your PC via only one direction of the Ethernet path from the FritzBox to the PC. And too much traffic will obscure what you are looking for. When you have it capturing, I think you can then unplug the FritzBox from the ONT, wait 10 seconds or so for it to disconnect (PPPoE takes a while to give up an existing connection), then plug it in again and capture the initial PPPoE negotiations. Then click on the Stop button and see what Wireshark can show you in the capture file.

Warning: If you have VOIP phone via the FritzBox, when you capture all the traffic, you will be recording any VOIP conversations happening at that time. If you are not a party to the phone call involved, that is illegal wiretapping and can get you a jail term. Make sure the phones are not being used! Including softphones! Wireshark makes it easy to just click on the VOIP traffic and play back the audio. The easy way to ensure no-one will be on the phone is to directly connect a laptop (or PC) to the FritzBox, unplug everything else on the LAN ports and the phone jack, and disable WiFi. Then do the capture from the laptop. That also minimises the amount of Internet traffic.

Wireshark is here:

https://www.wireshark.org

Cheers - I'll give this a go, probably on my next day off (Thursday) and bounce that through to 2Degrees if I can't remember how to wangle Wireshark correctly, been a while since I last used it.

c0ld

234 posts

Master Geek

#1976748 14-Mar-2018 20:57

I have exactly the same problem - "Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL)". Switched from 2degrees VDSL (IPv6 provisioned) to 2degrees Fibre and lost IPv6 immediately - this was back in April 2017.

We tried loads of stuff including a new fritz, packet traces, static IPs and so on but we finally gave up in September 2017 with no resolution - and still isn't fixed to this day. This is what we ended up with from Support (hopefully it makes sense without the full transcript) - maybe you can pass this on to see if they come to the same conclusion...

08/06/2017 - 2D Support

"So, we think this may be a bug with the fritz that’s hung around for a wee bit but we’ve never been able to get to the bottom of what’s happening or what triggers the bug. Its low impact enough that the investigation is

It looks like RADIUS and the BNG you are connecting to is passing on the assignment and the fritz either isn’t seeing it or is rejecting it somehow."

09/06/2017 - 2D Support "We’ve checked it out, and don’t think this is coming from the Fritzbox end, seems to be the BNG. I’ve left it with the engineering guys for now to check out, but will revisit with them on Monday and see what we can work out"

22/06/2017 - 2D Support "Just checked in with the system guys after being away, and sounds like we’re a bit stumped. I’m going to send you a fresh modem to try, just so we can be 100% sure whether it’s a bug in the modem, on the BNG, or account based. "

21/07/2017 - 2D Support

"Last I checked this was still under investigation, a handful of other affected accounts have been identified but no luck as yet replicating or forcing the issue. I think this may have even got to Juniper. I’ll check in with the team again this arvo and see where it’s at"

21/07/2017 - 2D Support

"Cool, so the guys are confused. Seems the BNGs are pushing out the addresses, but these either aren’t reaching the CPE, or the response from the CPE isn’t reaching the BNG They are currently working out a way to try and get some monitoring in the middle to see where it’s dropping from. I’ll keep you posted if they come up with anything J

18/08/2017 - 2D Support

"Just checked in on this with the engineering guys, we’re pretty confident this is resolved in later software versions, of which a roll out is planned and undergoing final testing at present. The decision was made against raising this further with Juniper as the likely answer would have been “fixed in later release” which was planned anyway. We’re certain it’s not configuration related. It is a big network wide roll out so the testing and roll out phase is quite detailed, once your part of the network has been done I’ll be sure to let you know J

26/09/2017 - 2D Support

"It’s with the Enterprise engineering team, and the fix is believed to be contained within future juniper software updates for the BNGs. An upgrade plan was already in place when this was identified, however that has been postponed due to critical defects being found in our standard testing process. There is literally nothing we can do until the BNGs are upgraded, and this is a major upgrade which will involve a nationwide rolling upgrade with periods of downtime for every single customer. There is no simple fix, and it’s a major piece of work."

Good luck!

darthmeow

101 posts

Master Geek

#1976849 15-Mar-2018 01:39

c0ld:

26/09/2017 - 2D Support

"It’s with the Enterprise engineering team, and the fix is believed to be contained within future juniper software updates for the BNGs. An upgrade plan was already in place when this was identified, however that has been postponed due to critical defects being found in our standard testing process. There is literally nothing we can do until the BNGs are upgraded, and this is a major upgrade which will involve a nationwide rolling upgrade with periods of downtime for every single customer. There is no simple fix, and it’s a major piece of work."

Good luck!

Ah bugger! That, doesn't fill me with the utmost of confidence but it does sound like it could be my issue as well. Still going to press on with a packet capture of the login process and see what I get there.

Aredwood

3885 posts

Uber Geek

#1979175 17-Mar-2018 20:28

Very interesting. I decided to finally get IPv6 working on my Edge router lite, And was getting frustrated as it was not working. I thought that I had a config error. But the above explains why I'm not having any luck with IPv6.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Note that to use Quic Broadband you must be comfortable with configuring your own router.

bonkas

314 posts

Ultimate Geek

#1981321 22-Mar-2018 08:37

Not sure if related but I have been struggling with this for a number of years with my pfSense setup. If you need logs or setup info let me know.

michaelmurfy

meow
13242 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1981335 22-Mar-2018 09:23

IPv6 is not working for me - you're not alone. This configuration did work in the past and nothing has changed.

It is just a waiting game I'm afraid...

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

2degreesCare

1537 posts

Uber Geek

Trusted

2degrees

#1995509 13-Apr-2018 14:10

Hi guys

Please can you let us know if you are still having any issues with this? We believe this is now resolved.

Cheers

^POB

darthmeow

101 posts

Master Geek

#1995562 13-Apr-2018 15:16

2degreesCare:

Hi guys

Please can you let us know if you are still having any issues with this? We believe this is now resolved.

Cheers

^POB

Nope. I did a reconnect on my router and I still have no IPv6. Same error as before: No response from DHCPv6 server (SOL). If it helps to narrow down the issue, the IPv4 says it's connecting to broadband PoP SNAP-104

c0ld

234 posts

Master Geek

#1995598 13-Apr-2018 15:58

darthmeow:

2degreesCare:

Hi guys

Please can you let us know if you are still having any issues with this? We believe this is now resolved.

Cheers

^POB

Nope. I did a reconnect on my router and I still have no IPv6. Same error as before: No response from DHCPv6 server (SOL). If it helps to narrow down the issue, the IPv4 says it's connecting to broadband PoP SNAP-104

Re-enabled IPv6, restarted router twice, same error unfortunately: 13.04.18 15:52:20 Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL).

Guessing my settings are correct (we played around with them quite a bit during troubleshooting) - please let me know if there's anything here I should be amending...

bonkas

314 posts

Ultimate Geek

#1995610 13-Apr-2018 16:28

No change here on a pfsense setup also.

RRman

38 posts

Geek

#1996335 15-Apr-2018 10:01

FRITZ!Box 7490

15.04.18

09:57:43

Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL).

15.04.18

09:57:24

Internet connection established successfully. IP address: 111.69.101.104, DNS server: 202.37.101.1 and 202.37.101.2, gateway: 111.69.7.69, broadband PoP: SNAP-69

tanivula

991 posts

Ultimate Geek

Lifetime subscriber

#1997168 16-Apr-2018 15:45

c0ld:

Re-enabled IPv6, restarted router twice, same error unfortunately: 13.04.18 15:52:20 Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL).

Guessing my settings are correct (we played around with them quite a bit during troubleshooting) - please let me know if there's anything here I should be amending...

I had a few issues getting ipv6 working when I had disabled and re-enabled it (moved the fritz a few times to other providers). I used to be stuck on Could not establish IPv6 Internet connection: No response from DHCPv6 server (SOL). on bigpipe. Anyways, back to 2deg and thought it was easy to get it working, but turned out it wasn't! Ended up having to do some messing around with the LAN side ipv6 settings. Will have a hunt and try and grab some screenies - might be useful for you.

1 | 2 | 3 | 4 | 5