Currently I have to use prefix length of /48 to get ipv6 to work, after these ONT upgrades does it mean I can use /56 again?

BlackHand:

 

Currently I have to use prefix length of /48 to get ipv6 to work, after these ONT upgrades does it mean I can use /56 again?

 

Hiya,

There were some earlier customers that were allocated a /48 (so I'm told).. so if we need to 'refresh' things, no issues, drop me a PM with your customer number once the upgrade is done and I'll get that sorted.

Nick.

Wahoo, it's back 

I dont know if this is hijacking the thread, im sorry if so.

Does anyone have a quick rundown on what settings are needed in pfsense, I tacked this a long time a go but have forgotten and not sure if my old thread is relevant anymore.

bonkas:

 

I dont know if this is hijacking the thread, im sorry if so.

 

Does anyone have a quick rundown on what settings are needed in pfsense, I tacked this a long time a go but have forgotten and not sure if my old thread is relevant anymore.

 

I'm with Voyager, but michaelmurfy's ERL guide indicated 2degrees used the same settings. That being the case, the settings below should work with pfSense.

On the WAN interface set IPv6 Configuration Type to DHCP6, check Use IPv4 connectivity as parent interface, and set the DHCPv6 Prefix Delegation size as allocated (/56).

On the LAN interface, set IPv6 Configuration Type to Track Interface, IPv6 Interface to WAN (or whatever you have named your WAN interface), and IPv6 Prefix ID to any value in the range pfSense indicates (00-ff on a /56).

hmm IPv6 is still showing offline. Do you have a link to the ERL guide? there may be something in there that will give me some hints on what im missing.

This is the guide https://www.geekzone.co.nz/forums.asp?forumid=66&topicid=205740

bonkas:

 

hmm IPv6 is still showing offline. Do you have a link to the ERL guide? there may be something in there that will give me some hints on what im missing.

 

I suspect it's just a matter of waiting until Chorus has deployed their updates and you should see IPv6 come to life on your network. Both pfSense and the ERL worked with basic configurations as soon as things were set up correctly.

No idea what ERL is. This is what I have on Mikrotik:

interface=pppoe-wan request=prefix add-default-route=yes default-route-distance=1 use-peer-dns=no pool-name="wan-ipv6" pool-prefix-length=64 prefix-hint=::/0 dhcp-options=""
 

Setting request to prefix only, and setting the pool to receive the prefix is all that was required IIRC.

Tracer:

 

No idea what ERL is.

 

ERL is Edgerouter Lite there are quite a few people here with them, and is the router used for Michael's guide that's linked above.

SirHumphreyAppleby:

bonkas:

hmm IPv6 is still showing offline. Do you have a link to the ERL guide? there may be something in there that will give me some hints on what im missing.

I suspect it's just a matter of waiting until Chorus has deployed their updates and you should see IPv6 come to life on your network. Both pfSense and the ERL worked with basic configurations as soon as things were set up correctly.

Hate digging up an old thread, but I believe it's blown up again. @NickMack and @BMarquis you may wish to know about this - Tuesday morning (16/04/2019) around 2:30AM or so I lost connection, as did a lot of my friends on other ISPs (Dad on Spark, friend on Spark, work on Spark Business, another friend on Vodafone - all at exactly the same time). Ever since this outage my IPv6 DHCPv6 client on my Mikrotik stalls at "Searching" as it did before the software upgrade. Did the outage brick something causing a software reversion or failover to other hardware that may have been on old software or am I just really unlucky? Any help with this is once again greatly appreciated!

darthmeow:

Hate digging up an old thread, but I believe it's blown up again. @NickMack and @BMarquis you may wish to know about this - Tuesday morning (16/04/2019) around 2:30AM or so I lost connection, as did a lot of my friends on other ISPs (Dad on Spark, friend on Spark, work on Spark Business, another friend on Vodafone - all at exactly the same time). Ever since this outage my IPv6 DHCPv6 client on my Mikrotik stalls at "Searching" as it did before the software upgrade. Did the outage brick something causing a software reversion or failover to other hardware that may have been on old software or am I just really unlucky? Any help with this is once again greatly appreciated!

NickMack:

darthmeow:

 

Hate digging up an old thread, but I believe it's blown up again. @NickMack and @BMarquis you may wish to know about this - Tuesday morning (16/04/2019) around 2:30AM or so I lost connection, as did a lot of my friends on other ISPs (Dad on Spark, friend on Spark, work on Spark Business, another friend on Vodafone - all at exactly the same time). Ever since this outage my IPv6 DHCPv6 client on my Mikrotik stalls at "Searching" as it did before the software upgrade. Did the outage brick something causing a software reversion or failover to other hardware that may have been on old software or am I just really unlucky? Any help with this is once again greatly appreciated!

 

Unless proven otherwise.. it's not a trend.. nothing has changed on our side from a hardware and software perspective.. so we will have to monitor ;-)

Thanks for that.