thanks, figured as much - just checking
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Which is the most hair-raising South African mountain pass you've driven?
IPv6 Roll Out
- Thread starter AfriNatic
- Start date
Not to hijack this thread. Our v6 over Openserve is native and isn't tunnelled (over both OBC and LNS networks). It's a dual stack implementation too. We just tunnel over Vuma trenched for the time being. Will drop you a PM
We do it native but it's not L2TP yet.
On Vumatel we have a /56. The only options on Vumatel will be /56 and /48
How would the setup on OS via Mikrotik differ to what we must do with AH?Not to hijack this thread. Our v6 over Openserve is native and isn't tunnelled (over both OBC and LNS networks). It's a dual stack implementation too. We just tunnel over Vuma trenched for the time being. Will drop you a PM
deweyzeph
Honorary Master
The Mikrotik configuration I detailed in the post above is for Openserve/Afrihost. I would assume it's more or less the same for any ISP running over Openserve.
deweyzeph
Honorary Master
I honestly can't remember why I have these particular settings, but I do know I used to have a lot of problems with my Windows 10 laptop hanging on to old IPv6 addresses when the prefix from Afrihost changed, and using these settings helped quite a bit.
since I tried to set it up earlier in this thread running routeros 6 it seems to be a lot more stable, no issues so far although i do not think my prefix has changed since I implemented it.
have you taken note of how often it changes? on each reconnect of pppoe?
deweyzeph
Honorary Master
The prefix changes every 24 hours. If you look under "IPv6 -> DHCP Client" you'll see that the prefix has an expiry time of 24 hours.
mine says 23hrs 47mins remaining but my ipv6 has not changed since I've taken note of it 18 hrs ago... will wait and see what happens in a few more hours.
TrueTenacity
Senior Member
Ohh I am sooo in on this... Let me know what you need?
TrueTenacity
Senior Member
I got it working on my Asus AX58U but as has been stated previously, everyone and everything loses connection when the prefix changes. So I'm sticking with IPv4 until there's a work-around for that...
Gimli_
Expert Member
@Afrigirl @AfriFella How far are you with static IPV6 Prefix Delegation on Openserve. I would really like not to have a different prefix every now and again
Last edited:
Gimli_
Expert Member
Crickets ****
This might be an option if we switch to LT2P but for now, it's not possible. The Prefix changes if the re-auth happens unexpectedly as the pre-fix is still in use.
BTW Vumatel Active Ethernet IPv6 is being rolled out and we expect to have IPv6 enabled for all Vumatel clients by the end of Feb. Dynamic prefixes with the option of a static prefix as long as the tech area doesn't change.
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.
Gambit
Expert Member
That is great that you secured a /28 prefix. Should allow 268 million /56 prefixes. Running out of /56 prefixes will be a good problem to have.
TheLostPacket
Well-Known Member
What about IPV6 for Axxess ?
btw ipv6 on mikrotik been going smoothly since I've tried it again - thanks for the config info.
i log ipv6 changes on my home assistant (of the home assistant host) and it's only changed 6 times between 8th Feb and today, so the lease doesn't necessarily change IP every 24h
