IPv6 Roll Out

Vumatel clients need to please enable Ipv6 in their routers.

We are in the final stages of implementation and clients will get a /56 PD and IA-NA from our new prefix 2c0e:7f00::/28

These are dynamic but are unlikely to change. We can set them to a static which will stay unless you change tech areas or relocate.
Hi @AfriNatic. How far is Afrihost from this being rolled out? I'm still getting the old 2c0f:f4c0:: /64 prefix
 
Last edited:
Hi @AfriNatic. How far is Afrihost from this being rolled out? I'm still getting the old 2c0f:f4c0:: /64 prefix

So for Vumatel active ethernet we now allocate a /56 but for gpon we still do a /62

If you have Vumatel active ethernet with an Object number I can now allocate a dynamic or static /56 pd and ia_na
 
Vumatel clients need to please enable Ipv6 in their routers.

We are in the final stages of implementation and clients will get a /56 PD and IA-NA from our new prefix 2c0e:7f00::/28

These are dynamic but are unlikely to change. We can set them to a static which will stay unless you change tech areas or relocate.
Turned it on but no dice on my end. Followed this guide : https://help.afrihost.com/entry/how-to-enable-a-dhcp-ipv6-on-the-tp-link-deco
Code:
DHCPv6 message arrived while DHCPv6 server is disabled
message arrived while RTADVD is disabled
 
Enabled it for you.

Please check again?

Whoop whoop but should it not be /56 since it’s Vuma trenched?

889e8c79695d1ccbfd6856d47258ca14.jpg


All ipv6 tests fail though.

Edit : Something changed over the last few hours. ISP listed as African Network Information Center - ( AfriNIC Ltd.
a49311e1758caa6b28515f9095e99a74.jpg
 
Last edited:
Whoop whoop but should it not be /56 since it’s Vuma trenched?

889e8c79695d1ccbfd6856d47258ca14.jpg


All ipv6 tests fail though.

Edit : Something changed over the last few hours. ISP listed as African Network Information Center - ( AfriNIC Ltd.
a49311e1758caa6b28515f9095e99a74.jpg

That looks fine. Everything is reachable. Seems your browser is preferring IPv4 over v6 for some reason. Maybe a setting?

With regards to the prefix length. It's one of the issues we raised when we were in discussion with the FNO. Most consumer-branded routers only pick and use a single /64 from the allocated prefix anyway so allocating a /56 to consumers means that 255 x /64 will never ever be used. It's the same type of thinking that caused IPv4 to get exhausted really.

That said you need a more advanced router to set vlans and make use of the /56 na and pd prefixes you are allocated. Consumer-based routers including the Huawei we supply currently won't use more than a /64.
 
That looks fine. Everything is reachable. Seems your browser is preferring IPv4 over v6 for some reason. Maybe a setting?

With regards to the prefix length. It's one of the issues we raised when we were in discussion with the FNO. Most consumer-branded routers only pick and use a single /64 from the allocated prefix anyway so allocating a /56 to consumers means that 255 x /64 will never ever be used. It's the same type of thinking that caused IPv4 to get exhausted really.

That said you need a more advanced router to set vlans and make use of the /56 na and pd prefixes you are allocated. Consumer-based routers including the Huawei we supply currently won't use more than a /64.
Upgraded my line speed for a bit and seems to have lost it.
 
Is it possible on Openserve yet?

I know I tried before but maybe something changed on your end.

Or what should the config be for Openserve now?

Yes it is. It's a dynamic prefix via DHCPv6. Please make sure to enable DHCPv6 and DHCPv6 via PD.
 
This is another ISP, but IPv6 on a mikrotik.

View attachment 1679801

A great example of how handy and nice IPv6 can be but not used by everyday consumers. If I can use my relatives as an example. They only know if the wifi is working or not working so for them they just need a working internet connection and so doing a /62 for them via dhcpv6 is ideal. It should just work.
 
Top
Sign up to the MyBroadband newsletter
X