Since it seems to be ipv6 month here at NZNog I thought I would bring this up.

 

Some of you have commented that Orcon is in trial mode for IPv6 and are probably wondering why we haven���t progressed.

 

We have had IPV6 enabled for a while and have a good number of ipv6 customers online now. However we found an issue on the Chorus network which stopped us rolling it out further. (UFB ipv6 was another battle which requires beer!)

 

What we found was some Chrous DSLAMS with certain card types would drop IPV6CP packets in one direction when doing the PPPoE->PPPoA conversation. It would seem that these cards don���t support Ipv6. Weirdly enough it would seem it is the newer card types used for Broadband IP. (citation needed). This in itself isn���t a major but we also found our NFV4 modem would reset its entire PPPoE stack if the IPV6CP conversation started but didn���t complete as expected, so customers would constantly be disconnected and cycle around. (The Genius modem works well with ipv6)

 

The NFV4 issue aside (we are resolving with the Vendor). We approached the Chorus tech team and they helped identify the issue but that���s is where its hit a brick wall. The Chorus op team are not keen on fixing the issue nationwide as it involves new code versions, a massive amount of testing and a long rollout program. (I can understand where they are coming from).

 

To summarise:

IPV6 doesn���t work on Chorus EUBA on some line card types

Only affect PPPoE->PPPoA translation

PPPoE end to end is fine.

Chorus say IPV6 not supported on EUBA

Customer numbers effected are smallish.

 

We will fix the NFV4 issue, but keen to rollout more IPV6 to all customers, not just the lucky ones on card types which work.

 

Has any other ISP���s (the bigger ones especially) noticed this? As it will require some pressure to get some progress.

 

Cheers,

Simon Allard

Orcon/Callplus