IPv6 Roll Out

@AfriNatic It's over a month now since you started this thread/trial. Any indication when Openserve will join this party?

For now Openserve, Vuma Reach and Vumatel is not part of the rollout due to various challenges with rolling that out.

All our other FNO's are being enabled. We have a large amount of subnets already enabled. We will be enabling Evotel for everyone soon. MetroFibre and Frogfoot Gauteng has been enabled for everyone.

As soon as the other are enabled I will let you know.
 
when it gets rolled out do previously non-CGN'd people get CGN'd on their v4?
 
when it gets rolled out do previously non-CGN'd people get CGN'd on their v4?

For now we will not be removing IPv4 public IP addresses.

Once we are comfortable with the IPv6 performance and reliability we will still allow public IPv4 addresses on a case by case basis.

Most people don't need public IP's and once we give them IPv6 the issues will be resolved but there is some clients that might still need a public IPv4 address and we would not refuse them one if required.
 
We have it enabled for 1 vlan in CPT and we do not have a lot of clients on that specific vlan.

If it's working you are on that specific vlan. :)
working on my parents + uncles FF so I guess they're on the working VLAN
 
working on my parents + uncles FF so I guess they're on the working VLAN

Let me know if you experience any issues. Also double check that it's working on

 
Let me know if you experience any issues. Also double check that it's working on

yea 10/10 on the test ipv6
 
I tested on a trial account from Websquad and can confirm native IPV6 on Openserve. Would you at least give us an idea of what your issue is, and a rough time line of when it will be activated. This is a question directed at the retentions department
 
I tested on a trial account from Websquad and can confirm native IPV6 on Openserve. Would you at least give us an idea of what your issue is, and a rough time line of when it will be activated. This is a question directed at the retentions department

As you may know we have been offering services on Openserve for quite a while. We have thousands and thousands of clients on legacy services like Copper Connect.

There is significant changes required for us to enable IPv6 on Openserve both on our and Openserve side.

I can assure you that IPv6 will be available for Openserve. We have been engaging the FNO in finding a solution to getting IPv6 enabled and supported. We have to make physical changes and we have to limit downtime for all clients.

As @websquadza mentioned they had the advantage of recently offering services on Openserve and were able to configure and arrange IPv6 from the get go.

Unfortunately I don't have an ETA for you as we are still in talks with Openserve on the best way forward.
 
v6 works on prefix delegation, not bridging. This means your /64 is allocated for your LAN network and is routed from the WAN.. Which means even a basic router usually runs a firewall protecting the LAN prefix (most routers we’ve checked support this).

Security by NAT is not secure at all- it’s laughably easy to bypass/spoof. Not to mention messy protocols like UPNP and the headaches NAT can cause (VoIP, games and more). So apples for apples - the firewall protecting you on v4 will do a similarly good job with v6 (likely even better). That said, it’s never a bad idea to get a firewall that supports DPI and some sort of threat intelligence (whether you’re using v4 or v6) to check inside all the packets passing through your network.

Standard rules to protect v6 on consumer routers cover forwarding v6 traffic to your delegated prefix based on established and related connections. Basically, inbound communication on IPv6 from the world is only allowed if the connection is established from behind the firewall (the same way it works on v4), or the connection is related. For persistent outside access (like accessing your CCTV), your firewall will need to have forwarding rules set up in your firewall filter list (no longer port forwarding the way we’re used to).
@websquadza would this be the kind of rule you need to set to protect your /64?

Screenshot 2021-04-21 at 11.57.50.png
 
As you may know we have been offering services on Openserve for quite a while. We have thousands and thousands of clients on legacy services like Copper Connect.

There is significant changes required for us to enable IPv6 on Openserve both on our and Openserve side.

I can assure you that IPv6 will be available for Openserve. We have been engaging the FNO in finding a solution to getting IPv6 enabled and supported. We have to make physical changes and we have to limit downtime for all clients.

As @websquadza mentioned they had the advantage of recently offering services on Openserve and were able to configure and arrange IPv6 from the get go.

Unfortunately I don't have an ETA for you as we are still in talks with Openserve on the best way forward.
Thanks for the honest reply. It is not as if Afrihost hasn't had plenty of time to address this before. I pinged Afrihost from time to time on this same forum over the past 5 plus years questioning about it. I have had very good service on my fibre account the past 3 years, so maybe one day I'll come back :-) But for now I will be trying the grass on the other side.
 
Any update on TTConnect. My router can connect to it, but there's no internet connection.
 
This rule looks like it will block all TCP/UDP traffic from reaching your /64. What firewall are you using?
Well the idea it to block remote inbound connections to the v6s... but not to stop all v6 traffic of course. this is just a Dlink DIR825
 
Top
Sign up to the MyBroadband newsletter
X