Heya @BMarquis, if you need info on what we're seeing on our side, hit me up :)

VygrNetworkMonkey:

Heya @BMarquis, if you need info on what we're seeing on our side, hit me up :)

BMarquis:

Yes, will do. If you guys can get a packet capture somewhere near the handover of one of the failing lines, it’d be handy to have as more info, but probably not necessary at the moment unless it’s easy for you to do.
I have a feeling the issue is less about the ONT type and more about the OLT line card.

I’m on leave at the moment, have some test scenarios being run in the lab as soon as we have some clear air to get an OLT downgraded.
The good news at the moment is we have tested with the new software and IPv6 (using @SirHumphreyAppleby packet capture) works OK.

We have PCAPs on both working an non-working circuits, including @SirHumphreyAppleby's circuit.

Our suspicions are similar to yours, as we're seeing some interesting stuff on the non-working circuits.

Let me know when you're back, and we'll send it all though :)

Well, we have some good news. Following the OLT/ONT software upgrade early this morning (thanks @BMarquis for keeping me informed), I am now getting IPv6 addresses assigned to my router and network.

Still no luck getting IPv6 working however. The ERL was left installed in what should have been a 'working' configuration based on michaelmurfy's tutorial, but sadly, no data was routed through the setup. I will need to try a complete reset of this later, but it's not my preferred platform.

pfSense shows similar behaviour, including after a factory reset. I have IPv6 addresses, they are assigned to hosts on the network, but nothing could talk out to the Internet, or so it appeared. A traceroute6 to Google from the router shows I am getting an initial response from 2406:1e00:9000::b:1 (lo-900-ip6.br1.mdr.vygr.net), but nothing beyond that.

That suggests to me the connection via Chorus is now fixed, but there is an upstream issue. @VygrNetworkMonkey, what do you think? Is there anything you need from me to help diagnose the issue?

SirHumphreyAppleby:

 

Success!

 

I now have a working IPv6 connection. Turns out I had also been allocated an address range from the wrong region.

 

Only outstanding issue is setting the PTR delegation for the new range, and I should be good to go.

 

Thanks everyone for their help with this issue.

 

Great to hear!

It looks like your prefix is delegated to he.net - is this where you are wanting it to go?

VygrNetworkMonkey:

 

Great to hear!

 

It looks like your prefix is delegated to he.net - is this where you are wanting it to go?

 

 

 

Yes, everything is sorted now.

Just got to enable IPv6 on the mail server and set up a few firewall rules, then I'll be fully operational again.

Good to see Voyager now have IPv6 when I last inquired they didn't

My ISP's IPv6 has stopped if they have withdrawn that (I should know tomorrow) I'll consider Voyager