South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
@AfriNatic @Afrigirl surely someone at AH's NOC uses Mikrotik? It's the poor man's cisco..
Would be nice to have an official tried and tested guide from someone who's trained on Mikrotik (not just a tinkerer like me) there are plenty MTK users around.
ipv6pd over pppoe (openserve) would be my wish.
Is anyone else in Afrihost with IPV6 running about to ping or run a trace to 2001:41d0:306:119d:: and tell me if it works for them?

Very strange :/
IPv6 has been around forever yet ISPs still can't get it reliably implemented
Back in July AfriNatic did say he was going to source a mikrotik and play around with it. I am thinking either he didn't or he realised that that are no where as user friendly as your off the shelf Netgear or TPlink home router. They really give you the ability to do anything but at the cost of complexity.
Just to add - I think the nzbfinder.ws address is ok - if I try to ping it using the website http://www.ipv6now.com.au/pingme.php and entering 2001:41d0:306:119d:: it works just fine. But from my side a traceroute to that address gives me this:
Code:Tracing route to mail.nzbfinder.ws [2001:41d0:306:119d::] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2c0f:f4c0:b166:9560::1 2 * * * Request timed out. 3 4 ms 5 ms 3 ms 2c0f:f4c0:3000:12::1 4 3 ms 2 ms 2 ms 2c0f:f4c0:3000:10::2 5 5 ms 1 ms 2 ms 2c0f:f4c0:3000:3::29 6 3 ms 2 ms 2 ms 2c0f:f4c0:3000:3::9 7 3 ms 3 ms 2 ms 2a01:410:1:1:46:17:239:46 8 5 ms 4 ms 4 ms 2001:42a8::41:171:133:44 9 10 ms 10 ms 9 ms 2001:42a8::41:171:132:67 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
SO it looks to me like something is getting lost on the afrihost routing side? Or am I wrong here?
If my firewall was blocking outgoing or incoming ICMPv6 packets then I would expect to have this issue with all addresses I try but it seems to only be some. As stated earlier I can ping and trace to 2600:: just fine. Yet to the above IP I get timeouts.It works fine on v6 for me. Please make sure that your firewall rules does not block ICMPv6 outgoing and incoming. Incoming especially. It causes fall back to v4 if the return packets get blocked and that is likely why the v6 testing websites time out on v6.
View attachment 1414413
If my firewall was blocking outgoing or incoming ICMPv6 packets then I would expect to have this issue with all addresses I try but it seems to only be some. As stated earlier I can ping and trace to 2600:: just fine. Yet to the above IP I get timeouts.
If you look at my post in post 870 you will see that I am timing out around hop 10. I do see that you and I are going out via different routers on the Afrihost side 2c0f:f4c0:3000.... vs 2c0f:f4c0:1000... could this in any way make a difference?
Here are both ipv4 and ipv6 traceroutes using ping plotter"Yes in JHB we are still egress via Cogent but in CPT Egress and Ingress is via Liquid telecoms.
Can you send me a v4 trace route?




It looks like Openserve right?
We only have issues on FNO's we run DHCP for where Tenda and Huawei LTE routers do not play fair. They distribute bogons over the L2 to other routers causing the issue. In some cases they even cause ICMPv6 floods.
Here are both ipv4 and ipv6 traceroutes using ping plotter"
View attachment 1414619
View attachment 1414621
Also worth adding that the https://test-ipv6.com/ has a failure for me too:
View attachment 1414625
According to that website the test that is failing uses the URL mtu1280.test-ipv6.zw.liquidtelecom.net - a ping to that also fails at the liquid telecoms stage:
View attachment 1414627
@AfriNatic is it possible my pppoe account has had ipv6 disabled on it (i have a static v4) somehow? i have the exact same settings as @atunguyd but it just stays on 'searching' for a prefix. it worked before a few months ago before I abandoned v6.
Openserve, correct but I'm using a Dlink fibre/LTE router





Hi all,
So I decided to try IPv6 again.....but...not the best so far.
I'm using a ASUS RT-AC86U router with Merlin WRT 386.7_2 firmware (mostly for the Diversion ad-blocking)
I have tried in the past, but have had some issue every time.
1st, I have disabled the Diversion part, as it just resulted in NO connectivity at all...even though they say IPv6 is supported.
2nd, not sure about the correct settings? These are the options in the Router dashboard.
View attachment 1416731
Chose Native, and this is the connection settings after reboot:
View attachment 1416735
So getting a IPv6 assigned.
The assigned DNS servers are:
View attachment 1416739
I take it those are AfriHost DNS.
The IPv6 test sites give me:
View attachment 1416751
and
View attachment 1416749
But still get errors like these:
C:\>ping google.com
Pinging google.com [2c0f:fb50:4002:800::200e] with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.
Ping statistics for 2c0f:fb50:4002:800::200e:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
So, anyone had luck with ASUS routers & Merlin firmware & Diversion?
For now, as long as the IPv6 connectivity works, I will make a plan for the ad-blocking if needs be (PiHole to the rescue again)
Any idea what is wrong, what I'm doing wrong...?
(PS saw now, that same test-ipv6.com site on my phone gave a 10/10 score....wth?)
Ta
What options do you have for Ipv6?
With TP-Link they do not work on DHCPv6 but instead needs the Non-address option enabled. This might be a similar case for the D-link
Standard prefix delegation with a /60 on Openserve - it gets a subnet just fine, clients get their own IPs, everything -should- work
but no connectivity over IPv6. Packets have no route.