IPv6 Roll Out

@Afrigirl, I'm trying to configure IPv6 on my Unifi UCG but documentation is a bit scarce on what and how it needs to be configured -- especially when it comes to what the PD value is that should be used.

My FNO is Octotel and I can see that my router gets an IPv6 address when configuring it to use DHCPv6 but it does not show the prefix. With some research and logging on the router I can see that a /56 is returned but still cannot get it working. Setting it to Auto, /64, /56, pretty much anything does not seem to work.

FYI: definitely need more than a /64

Any suggestions / help
 
Fsh said:
@Afrigirl, I'm trying to configure IPv6 on my Unifi UCG but documentation is a bit scarce on what and how it needs to be configured -- especially when it comes to what the PD value is that should be used.

My FNO is Octotel and I can see that my router gets an IPv6 address when configuring it to use DHCPv6 but it does not show the prefix. With some research and logging on the router I can see that a /56 is returned but still cannot get it working. Setting it to Auto, /64, /56, pretty much anything does not seem to work.

FYI: definitely need more than a /64

Any suggestions / help
Click to expand...
Update — with the help of my clever friend Claude, I dug into this at the packet level. The DHCPv6 side turns out to work perfectly; the fault is one specific thing on the routing side.

Working: IA_NA (WAN address), and IA_PD — tested with Auto, /64, /56, and /48 hints; the server answers every one with the same delegated prefix: 2c0e:7f02:xxxx:x00::/56, sane lifetimes. Full pcap of the exchanges available.

Broken: the delegated /56 has no return route to my circuit. Traffic sourced from the delegated prefix gets zero return packets — tcpdump on my WAN shows echo requests egressing with nothing coming back — while the same router, same moment, pinging from its WAN (IA_NA) address gets ~2.5ms to Cloudflare.

Control test: an arbitrary extra address added inside the WAN on-link /64 (2c0f:f4c0:xxxx::/64) is fully reachable — the BNG resolves it via ND and traffic flows normally. So routing works for the on-link /64 and specifically not for the PD prefix.

Conclusion: on my circuit, the DHCPv6 server delegates a prefix correctly, but there's no route for the delegated prefix back to me.
 
Fsh said:
Update — with the help of my clever friend Claude, I dug into this at the packet level. The DHCPv6 side turns out to work perfectly; the fault is one specific thing on the routing side.

Working: IA_NA (WAN address), and IA_PD — tested with Auto, /64, /56, and /48 hints; the server answers every one with the same delegated prefix: 2c0e:7f02:xxxx:x00::/56, sane lifetimes. Full pcap of the exchanges available.

Broken: the delegated /56 has no return route to my circuit. Traffic sourced from the delegated prefix gets zero return packets — tcpdump on my WAN shows echo requests egressing with nothing coming back — while the same router, same moment, pinging from its WAN (IA_NA) address gets ~2.5ms to Cloudflare.

Control test: an arbitrary extra address added inside the WAN on-link /64 (2c0f:f4c0:xxxx::/64) is fully reachable — the BNG resolves it via ND and traffic flows normally. So routing works for the on-link /64 and specifically not for the PD prefix.

Conclusion: on my circuit, the DHCPv6 server delegates a prefix correctly, but there's no route for the delegated prefix back to me.
Click to expand...
You are setting up the /56 on the WAN correct? And then setting prefix delegation on the LAN side for each VLAN?

Edit: On Openserve I had to use SLAAC on WAN with /56 then PD on LANs
 
Mzezman said:
You are setting up the /56 on the WAN correct? And then setting prefix delegation on the LAN side for each VLAN?

Edit: On Openserve I had to use SLAAC on WAN with /56 then PD on LANs
Click to expand...
Correct on the WAN and LAN setups.

From what I've gather SLAAC is only for Openserve and Vodacom based on Afrihost documents-- but regardless, I did try SLAAC and got no response back from the other side
 
Fsh said:
Correct on the WAN and LAN setups.

From what I've gather SLAAC is only for Openserve and Vodacom based on Afrihost documents-- but regardless, I did try SLAAC and got no response back from the other side
Click to expand...
On Afrihost(Openserve) it is DHCP6 on the WAN, and on the Lan you can use SLAAC. On a pfsense or opensense router you have to set 'track interface' on the lan equal to 'WAN' so that it knows to use the prefix provided by the WAN. Make sure you enable 'Router advertisements'
Openserve provides a /60 but I also heard Octotel provides a /56. I don't know how this differs from UnifiOS, but I hope the above helps

PS. The DHCP6 on the wan is not to delegate prefixes to the LAN, it is to get a prefix from the ISP. It uses the IPv4 PPPOE connection to obtain the IPV6 Prefix.
 
Last edited:
Fsh said:
Update — with the help of my clever friend Claude, I dug into this at the packet level. The DHCPv6 side turns out to work perfectly; the fault is one specific thing on the routing side.

Working: IA_NA (WAN address), and IA_PD — tested with Auto, /64, /56, and /48 hints; the server answers every one with the same delegated prefix: 2c0e:7f02:xxxx:x00::/56, sane lifetimes. Full pcap of the exchanges available.

Broken: the delegated /56 has no return route to my circuit. Traffic sourced from the delegated prefix gets zero return packets — tcpdump on my WAN shows echo requests egressing with nothing coming back — while the same router, same moment, pinging from its WAN (IA_NA) address gets ~2.5ms to Cloudflare.

Control test: an arbitrary extra address added inside the WAN on-link /64 (2c0f:f4c0:xxxx::/64) is fully reachable — the BNG resolves it via ND and traffic flows normally. So routing works for the on-link /64 and specifically not for the PD prefix.

Conclusion: on my circuit, the DHCPv6 server delegates a prefix correctly, but there's no route for the delegated prefix back to me.
Click to expand...
Reach out to the Afrihost NOC team via mail for assistance. ask them to give you a test pppoe account if they insist the issue is on your end. If it works on pppoe that will show they are dropping the ipv6 packets on your dhcpv6 config, you get the PD, but it is not usable because the ipv6 packets are dropped.
 
Last edited:
13en said:
Reach out to the Afrihost NOC team via mail for assistance. ask them to give you a test pppoe account if they insist the issue is on your end. If it works on pppoe that will show they are dropping the ipv6 packets on your dhcpv6 config, you get the PD, but it is not usable because the ipv6 packets are dropped.
Click to expand...
Fsh said:
Update — with the help of my clever friend Claude, I dug into this at the packet level. The DHCPv6 side turns out to work perfectly; the fault is one specific thing on the routing side.

Working: IA_NA (WAN address), and IA_PD — tested with Auto, /64, /56, and /48 hints; the server answers every one with the same delegated prefix: 2c0e:7f02:xxxx:x00::/56, sane lifetimes. Full pcap of the exchanges available.

Broken: the delegated /56 has no return route to my circuit. Traffic sourced from the delegated prefix gets zero return packets — tcpdump on my WAN shows echo requests egressing with nothing coming back — while the same router, same moment, pinging from its WAN (IA_NA) address gets ~2.5ms to Cloudflare.

Control test: an arbitrary extra address added inside the WAN on-link /64 (2c0f:f4c0:xxxx::/64) is fully reachable — the BNG resolves it via ND and traffic flows normally. So routing works for the on-link /64 and specifically not for the PD prefix.

Conclusion: on my circuit, the DHCPv6 server delegates a prefix correctly, but there's no route for the delegated prefix back to me.
Click to expand...
FYI... @Afrigirl reached on Saturday just after I posted this and got it all sorted out for me today -- not exactly sure what they did on their side, but EXCELLENT service!
 
Fsh said:
FYI... @Afrigirl reached on Saturday just after I posted this and got it all sorted out for me today -- not exactly sure what they did on their side, but EXCELLENT service!
Click to expand...
@AfriNatic is the one that reached out. I only came online today. Thank you for for your cooperation, the team and our providers were able to find the issue with our Ipv6 configuration.
 
Any updates on Frogfoot IPv6?

I noticed today my router showing a WAN IPv6 but not sure on what the configuration should be...
 
For the last 2 weeks my ipv6 suddenly stopped working after a fiber outage. I realised this as home asssitant was not connexting to nabu, and was getting timeouts with ipv6 turned on.
When i did a an ipv6 test. I get this error message. “Connections to IPv6-only sites are timing out. Any website that is IPv6 only, will appear to be down to you.” I asked afrihost via support chat and was told by their supervisor : They advised they cannot actually enable the IPV6 as there is issues with it.
Im with link layer
 
AfriNatic said:
Good afternoon everyone!

As most people know IPv4 resources is getting fewer as time is going on.

We are setting up a trial to roll out IPv6 and would like to know if anyone is interested in joining this trial.

For now we can discuss interest and concerns in this thread while we work to get it setup in the next week or so. :)
Click to expand...
What is ipv6
 
@Afrigirl Are these settings correct for an Openserve fibre line?


Everything is working fine, but I’m just unsure whether my IPv6 settings are correct, as I couldn’t find a Afrihost setup guide specifically for TP-Link routers, only for the Deco Mesh.


According to your Deco help article, under IPv6 LAN → Assigned Type, the setting should be DHCPv6. However, when I select DHCPv6 on my TP-Link router, IPv6 doesn’t seem to work. If I change it to SLAAC+Stateless DHCP, IPv6 works fine.


Is SLAAC+Stateless DHCP the correct setting to use in this case, or should I be using DHCPv6?
 

Attachments

  • IMG_0270.jpeg
    IMG_0270.jpeg
    56.7 KB · Views: 15
  • IMG_0271.png
    IMG_0271.png
    335.2 KB · Views: 15
  • IMG_0272.png
    IMG_0272.png
    285.1 KB · Views: 15
mathebus said:
@Afrigirl Are these settings correct for an Openserve fibre line?


Everything is working fine, but I’m just unsure whether my IPv6 settings are correct, as I couldn’t find a Afrihost setup guide specifically for TP-Link routers, only for the Deco Mesh.


According to your Deco help article, under IPv6 LAN → Assigned Type, the setting should be DHCPv6. However, when I select DHCPv6 on my TP-Link router, IPv6 doesn’t seem to work. If I change it to SLAAC+Stateless DHCP, IPv6 works fine.


Is SLAAC+Stateless DHCP the correct setting to use in this case, or should I be using DHCPv6?
Click to expand...
Looks OK to me, the SLAAC is on the LAN side. On the WAN side it is DHCP6 with prefix delegation, on top of your existing IPV4 connection.

Via a web browser test your connection at https://test-ipv6.run/

If you get 10/10 for IPV6 and IPV4 you are fine
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X