IPv6 Roll Out

There is no timeline yet, and our biggest project is to move all clients to PPPoE before the end of next year.
I believe once that is done, we should be able to offer static prefix
May I ask what's the reason/difference between some ISPs using DHCP vs PPPoE?
 
May I ask what's the reason/difference between some ISPs using DHCP vs PPPoE?
It is a choice; however, we have encountered some security measures with other FNOs that cannot be made to work properly for DHCP.
 
Anyone have configs for OPNsense on Octotel?
Not sure if Prefix 60 is correct.
I am getting enormous delays when enabling IPv6 on every page as well as every app that uses the internet.
Once I disable IPv6 on Windows directly the issue is instantly resolved, so I assume it's related to my configuration.

Any ideas? @Afrigirl @AfriGuy @AfriNatic

Screenshot 2024-12-19 015128.png
Screenshot 2024-12-19 at 01-58-56 WAN Interfaces merlin-portal.gateway.png
 

Attachments

  • Screenshot 2024-12-19 015128.png
    Screenshot 2024-12-19 015128.png
    223.8 KB · Views: 30
Last edited:
Morning @Afrihost team,

For some reason my IPV6 address is no longer being allocated by DHCP6, could you please take a look and see if there is some kind of config issue?

Thanks
 
Migrating from Frogfoot to Octotel and testing IPv6. On Frogfoot, I get a /62 PD, so I can only run IPv6 on 4 VLANs (one per /64). That’s why I’ve only enabled it on my guest VLAN so far.

Does anyone know what PD size Octotel offers? Hoping for at least a /56 so I can dual-stack more VLANs.

Currently using interface tracking + RA in Unmanaged mode (pure SLAAC) for address assignment — see attached screenshots of my config. Curious if others running multi-VLAN IPv6 at home recommend sticking with this approach or doing something else.

This is for my frogfoot setup:
WAN:
1746626458318.png

Guest VLANconfig:


1746625586986.png

Router advertisements:

1746626277349.png
 
Migrating from Frogfoot to Octotel and testing IPv6. On Frogfoot, I get a /62 PD, so I can only run IPv6 on 4 VLANs (one per /64). That’s why I’ve only enabled it on my guest VLAN so far.

Does anyone know what PD size Octotel offers? Hoping for at least a /56 so I can dual-stack more VLANs.

Currently using interface tracking + RA in Unmanaged mode (pure SLAAC) for address assignment — see attached screenshots of my config. Curious if others running multi-VLAN IPv6 at home recommend sticking with this approach or doing something else.

This is for my frogfoot setup:
WAN:
View attachment 1818663

Guest VLANconfig:


View attachment 1818659

Router advertisements:

View attachment 1818662

I tried switching over to IPv6 (Openserve/Afrihost) and it works, however until they come out with static prefixes that don't change every 24 hours it's actually pretty frustrating to work with.
 
Migrating from Frogfoot to Octotel and testing IPv6. On Frogfoot, I get a /62 PD, so I can only run IPv6 on 4 VLANs (one per /64). That’s why I’ve only enabled it on my guest VLAN so far.

Does anyone know what PD size Octotel offers? Hoping for at least a /56 so I can dual-stack more VLANs.

Currently using interface tracking + RA in Unmanaged mode (pure SLAAC) for address assignment — see attached screenshots of my config. Curious if others running multi-VLAN IPv6 at home recommend sticking with this approach or doing something else.

This is for my frogfoot setup:
WAN:
View attachment 1818663

Guest VLANconfig:


View attachment 1818659

Router advertisements:

View attachment 1818662
You should request a /56 prefix from AH, that is the recommended size for residential users and is BCOP 690, that along with stable / static prefixes. "a /48 could be assigned to every human for the next 480 years before they run out."
 
Last edited:
I tried switching over to IPv6 (Openserve/Afrihost) and it works, however until they come out with static prefixes that don't change every 24 hours it's actually pretty frustrating to work with.
Agreed the dynamic prefixes are a pain to deal with, why can't we have stable prefixes, as per the RIR recommendations, while we're at it when is ZA going to get v6 on mobile, dual stack if need be so devices that have clat can run v6 only and free up resources on provider NAT boxes.
 
Agreed the dynamic prefixes are a pain to deal with, why can't we have stable prefixes, as per the RIR recommendations, while we're at it when is ZA going to get v6 on mobile, dual stack if need be so devices that have clat can run v6 only and free up resources on provider NAT boxes.

Yeah, I've switched off IPv6 on my network now until the network providers can provide static prefixes.
 
Another request for static (or unchanging DHCPv6-provided) IPv6 prefixes! (I'm using PPPoE on Openserve)

Dynamic prefixes are painful to deal with and cause all sorts of weird issues and annoyances, especially after power outages (the old prefix isn't deprecated so devices still cling to it causing connectivity problems).
 
Another request for static (or unchanging DHCPv6-provided) IPv6 prefixes! (I'm using PPPoE on Openserve)

Dynamic prefixes are painful to deal with and cause all sorts of weird issues and annoyances, especially after power outages (the old prefix isn't deprecated so devices still cling to it causing connectivity problems).

Yes, this is the exact problem I had. It boggles the mind why static IPv6 prefixes aren't standard, there's really no reason why they shouldn't be.
 
Can't you set the expiry time sent to clients to a lower value? Similar to a dhcp lease expiring. If its low enough, should be fine when the ipv6 prefix changes. At least in theory.
 
Can't you set the expiry time sent to clients to a lower value? Similar to a dhcp lease expiring. If its low enough, should be fine when the ipv6 prefix changes. At least in theory.
We should not have to be make use of workarounds like we did in v4 land, providers should give us static prefixes, what is the reasoning behind the dynamic PD's, some used to say rotate for privacy, The RFC's were updated years ago to address such concerns, the hosts now have temp/ rotating IP's for privacy , so there really is no need for providers to still be using dynamic prefixes if they follow the RIR's BCOP
 
We should not have to be make use of workarounds like we did in v4 land, providers should give us static prefixes, what is the reasoning behind the dynamic PD's, some used to say rotate for privacy, The RFC's were updated years ago to address such concerns, the hosts now have temp/ rotating IP's for privacy , so there really is no need for providers to still be using dynamic prefixes if they follow the RIR's BCOP
Yes that is should, but right now, you have no choice.
 
Top
Sign up to the MyBroadband newsletter