IPv6 Roll Out

AfriNatic said:
Yes it does. Please do dual stack PPPoE with DHCPv6 and /62 Prefix Delegation.
Click to expand...
Right, I have prefix delegation and my USG is setup for DHCPv6 on PPPoE, but not getting an IP. Will check if there are some weird Unifi related things I have to set.
 
Anyone with a USG3p / PPPoE (so I guess Vodacom and OpenServe) that have working IPv6? Stuck at

sent [IPV6CP ConfReq id=0x1 <addr xxx>]
sent [IPV6CP ConfReq id=0x1 <addr xxx>]
sent [IPV6CP ConfReq id=0x1 <addr xxx>]
sent [IPV6CP ConfReq id=0x1 <addr xxx>]
IPV6CP: timeout sending Config-Requests

dhcp6c seems to be correctly configured to use pppoe0 with prefix /62, but I am not getting an IPv6 assigned to my PPPoE session.
 
Has the configuration for Openserve changed?

My UDM Pro doesn’t seem to get an IPv6 any more but could also be early release firmware related.

****

@AfriNatic May be a good idea to update the first post with standard setting per FNO and even possibly per router brand?
 
Last edited:
SauRoNZA said:
Has the configuration for Openserve changed?

My UDM Pro doesn’t seem to get an IPv6 any more but could also be early release firmware related.

****

@AfriNatic May be a good idea to update the first post with standard setting per FNO and even possibly per router brand?
Click to expand...

Are you still without an IPv6? I don't seem to get one on my USG3p.
 
Strange said:
Are you still without an IPv6? I don't seem to get one on my USG3p.
Click to expand...

Yeah for lack of any responses didn’t try again.

The lack of any basic documentation with this rollout is actually quite frightening.
 
Strange said:
Are you still without an IPv6? I don't seem to get one on my USG3p.
Click to expand...

SauRoNZA said:
Yeah for lack of any responses didn’t try again.

The lack of any basic documentation with this rollout is actually quite frightening.
Click to expand...

It seems like we are running IPv6 in a bit of an odd way which some routers do not like. We do a /128 for the IA-NA and a /62 for Prefix Delegation. Some routers do not like this and some FNO's and manufacturers suggested we do a /64 for the IA and between a /48 to /60 for the PD. It doesn't make sense to us to waste this much of address space.

The setup is pretty simple depending on the router.

If you are on PPPoE the IPv6 part is DHCPv6 with a /62 PD. Some routers need you to set dual stack PPPoE and not separate wan interfaces for v4 and v6. Some routers like TP-link need to have IPv6 set as a Non-address because we use the /128 for the IA the TP-link wants to allocate addresses from this allocated prefix which is not possible because it's a single address on the WAN so setting non-address it will ask for the /62 pd and delegate that to lan connected devices.

There is no set guide how to configure routers because each manufacturer seems to name and implement it their way that is why support wise we support the routers we supply. We can try to assist with 3rd party routers but since we haven't tested configurations our guess sometimes are as good as yours.
 
AfriNatic said:
It seems like we are running IPv6 in a bit of an odd way which some routers do not like. We do a /128 for the IA-NA and a /62 for Prefix Delegation. Some routers do not like this and some FNO's and manufacturers suggested we do a /64 for the IA and between a /48 to /60 for the PD. It doesn't make sense to us to waste this much of address space.

The setup is pretty simple depending on the router.

If you are on PPPoE the IPv6 part is DHCPv6 with a /62 PD. Some routers need you to set dual stack PPPoE and not separate wan interfaces for v4 and v6. Some routers like TP-link need to have IPv6 set as a Non-address because we use the /128 for the IA the TP-link wants to allocate addresses from this allocated prefix which is not possible because it's a single address on the WAN so setting non-address it will ask for the /62 pd and delegate that to lan connected devices.

There is no set guide how to configure routers because each manufacturer seems to name and implement it their way that is why support wise we support the routers we supply. We can try to assist with 3rd party routers but since we haven't tested configurations our guess sometimes are as good as yours.
Click to expand...
I'm not an expert on this but I remember reading years ago that it was best practice for ISPs to delegate /56 prefixes as a minimum but with /48 prefixes being preferred, especially for business customers. There are more IPv6 addresses than atoms in the universe or something like that so if you are running out of address space assigning /48's then request more from the RIR.
 
Gambit said:
I'm not an expert on this but I remember reading years ago that it was best practice for ISPs to delegate /56 prefixes as a minimum but with /48 prefixes being preferred, especially for business customers. There are more IPv6 addresses than atoms in the universe or something like that so if you are running out of address space assigning /48's then request more from the RIR.
Click to expand...

It just doesn't make sense to give someone who watches Netflix a /56. That is 256 /64 "networks"

It's a lot of address space to just waste that will NEVER be used. Even at a /62 it gives clients 2 x /64 blocks to work with if they want to play around with custom IPv6 address names.

For point to point it's recommended to allocate a /64 which just doesn't make sense. Staying within nibble boundaries is great to keep things simple but it wastes a lot of addresses. Who knows what will happen 50 years from now?
 
AfriNatic said:
It just doesn't make sense to give someone who watches Netflix a /56. That is 256 /64 "networks"

It's a lot of address space to just waste that will NEVER be used. Even at a /62 it gives clients 2 x /64 blocks to work with if they want to play around with custom IPv6 address names.

For point to point it's recommended to allocate a /64 which just doesn't make sense. Staying within nibble boundaries is great to keep things simple but it wastes a lot of addresses. Who knows what will happen 50 years from now?
Click to expand...
I will be honest, a /62 will not work for me.

When running multiple vlans, and I have more than just 2, what is a /62 going help? 2x /64s is then not enough.

Currently my network is split into 6 vlans for security purposes, to isolate different things on the network. I do not trust the chinese home automation devices one bit, so they all on their vlan. Cameras on their own vlan. User devices on a vlan. Trusted opensource iot on a vlan. Servers on a vlan. Etc.

A /48 is a good choice. Even as an ISP, you should not run out of IPv6 space, and I am sure you can easily get more if you have in fact used up the 1st prefix you received.

I know I know, I am in the minority. It just means, with a /62 I will end up not using IPv6.
 
Found a nice blog post about IPv6 addressing for customers on Afrinic.

Simplifying IPv6 Addressing of Customers

One of the main issues when an ISP is planning to deliver IPv6 services is to decide how to address the customers. In a generic way, we could say that the first thing to do for any IPv6 deployment is the complete network addressing plan, even before obtaining your addressing space from your...
afrinic.net afrinic.net

conclusions
5.2 It is strongly discouraged to assign prefixes longer than a /56, so your choices are:

  1. My recommendation and if you want a simple addressing plan, assign a /48 to each customer. This will work very well for customers coming from other ISPs, those that have their own ULA, or have been using transition mechanisms. This will also be easier when you have a mix of customers using the same infrastructure, whether they are residential customers, SMEs or even large corporates.
  2. Differentiate among types of customers, even if this will increase the complexity of your network and those of your customers. Offer a /48 to business customers and a /56 for residential customers. As explained, this is not future proof and some new protocols will not work, so consider it carefully as it may mean that sooner or later you need to redo the plan and renumber.
  3. A compromise could be to reserve a /48 for residential customers, but actually just assigning them the first /56.
Click to expand...
 
I am not sure the architect at Afrihost understand how IPv6 work if they think a /128 for IA-NA and /62 for ULA is more than enough.

Most routers obviously don't like a /128 and heck a /64 is nice because then you can always use ::1 and ::2 at the end for the device on each end. For the prefix delegation for the lan side, using a /48 makes it easy for the router to just dynamically hand out a /64 per vlan.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X