tanivula: @c0ld

These are the settings that work for me on 2deg fibre.

For internet:


And in LAN:

A massive thanks for taking the time to post those settings but same issue / error message unfortunately. Pretty confident the issue is somewhere between the ONT and Chorus / my ISP. 

Still not working for me on a Edgerouter.

Out of curiosity what prefix-length are Edgerouter users using /56 - /64? Would that make a difference?

c0ld:

 

tanivula: @c0ld

These are the settings that work for me on 2deg fibre.

For internet:


And in LAN:

 

A massive thanks for taking the time to post those settings but same issue / error message unfortunately. Pretty confident the issue is somewhere between the ONT and Chorus / my ISP. 

 

Nope. Still broken. @2degreescare any help here please? Greatly appreciated!

BlackHand:

 

Still not working for me on a Edgerouter.

 

Out of curiosity what prefix-length are Edgerouter users using /56 - /64? Would that make a difference?

 

 

 

2degrees provides a /56 for IPv6.  You definitely need to be using the correct settings for that.  Do you pay for static IP addreses?  The setup for that can be done using just the static address, instead of having to negotiate with the 2D router to get the address and then delegate it.  You can find your static addresses by logging in to your 2D account and looking at the summary page.  The setup for that is much simpler.

fe31nz:

 

The setup for that can be done using just the static address, instead of having to negotiate with the 2D router to get the address and then delegate it.  You can find your static addresses by logging in to your 2D account and looking at the summary page.  The setup for that is much simpler.

 

At the moment affected connections won't be able to use IPv6 at all - even if using a static IP.

I'm affected by the issue too, and manually configuring a static didn't help.

I transitioned to 2d today but have been unable to obtain a v6 prefix. The symptoms on my end appear identical to that of others in this thread. I'm on UFB in Auckland.

I spoke with support who told me this is happening due to a Chorus issue. I queried as to whether there were any other details on this, but the person I spoke with couldn't provide any. I queried whether I could be kept informed as to the progress of the issue with Chorus via email, but was told no. I'd have to call in again.

Does anyone know if this is a localised issue, or is it Chorus wide?

Lorenceo:

 

I transitioned to 2d today but have been unable to obtain a v6 prefix. The symptoms on my end appear identical to that of others in this thread. I'm on UFB in Auckland.

 

I spoke with support who told me this is happening due to a Chorus issue. I queried as to whether there were any other details on this, but the person I spoke with couldn't provide any. I queried whether I could be kept informed as to the progress of the issue with Chorus via email, but was told no. I'd have to call in again.

 

Does anyone know if this is a localised issue, or is it Chorus wide?

 

I would say it's more widespread as I'm in Palmerston North experiencing this.

@NickMack got any information here?

On my radar too.

We (Chorus) are investigating. Its complicated further as we have an impending OLT and ONT software upgrade coming, so we have a few extra pieces to test and, if it is a Chorus issue, figure out what the fix is and where/when it is best applied.
It doesnt seem to affect all connections, only some.

Will update here as much as I can to save you phone calls.

michaelmurfy:

 

@NickMack got any information here?

 

Hi Master Murphy :-)

Just checked in with the team - We have a number of customers experiencing an issue with IPv6 on the Chorus network, vast majority in the North Island. We've done a fair amount of testing (tunneling of traffic to other BNGs for example) which hasn't been fruitful. We have a couple of tickets open with Chorus to investigate - I'll post an update once more information comes to hand.

Nick

Hi All,

A bit more info - The examples we have supplied to Chorus are potentially related to the FGLT-B card (fibre card on Chorus end) with its behaviour on PPPoE-based connections. This is yet to be proven however this is where the current troubleshooting is being focused. Chorus is gathering further information (from us and I suspect others) and working with Nokia. It appears that the CPE's are not receiving the IPv6 Router advertisements.

Nick.

HI All;

Small update - additional packet captures from the core & customer side have been supplied, this is under active investigation by the hardware vendor.

Nick.

NickMack:

 

HI All;

 

Small update - additional packet captures from the core & customer side have been supplied, this is under active investigation by the hardware vendor.

 

Nick.

 

Excellent news. Thank you for the hard yards. Looking forward to resolution :)

NickMack:

 

HI All;

 

Small update - additional packet captures from the core & customer side have been supplied, this is under active investigation by the hardware vendor.

 

Nick.

 

Yep, this is right.
We've had a case open with Nokia for a few days now.  Today we had it escalated.

Without wanting to predetermine the outcome, I'm picking the resolution will likely occur with the OLT and ONT upgrades which will be in a couple of months or so. (Unless Nokia come back with some kind of configuration workaround/fix rather than a software based fix.)