[afnog] IPv6 transition mechanism used by ISP

JORDI PALET MARTINEZ jordi.palet at consulintel.es
Mon Dec 3 10:00:52 UTC 2018


By the way.

 

Some CPE vendors already support it, but not in the retail models. This was explained in my presentation this week “Raiders of the lost Ark” “in search for the lost CPE”.

 

https://meeting.afrinic.net/afrinic-29/components/com_afmeeting/speakers/3283/raiders-of-the-lost-ark-Jordi-Palet.pdf

 

Not sure when video will be available …

 

The big offender is Mikrotik, they don't support any transition mechanism except 6in4 and this is now useless once you exhaust IPv4 addresses. They are so negligent that they even confuse people using “6to4” to say “6in4”, and those are 2 different transition mechanisms. Not sure how much is being used in residential users in Africa … they are the big offender (I think also Ubiquity). Just don’t by them, or reflash them with OpenWRT and make sure to tell the vendor about it. Only market pressure will make them react.

 

And of course, we have open source. I will suggest Jool for both the NAT64 and CLAT, but there are other choices.


Regards,

Jordi

 

 

 

De: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>
Fecha: lunes, 3 de diciembre de 2018, 10:48
Para: Mark Tinka <mark.tinka at seacom.mu>, Diarmuid O Briain <diarmuid at obriain.com>, UIXP Techies <techies at uixp.co.ug>, <afnog at afnog.org>
Asunto: Re: [afnog] IPv6 transition mechanism used by ISP

 

Android and Windows support since several years ago.

 

In Apple phones is not needed because they mandate the support of IPv6 in apps. You only have the problem of tethering, but Apple has implemented the CLAT as well for tethering a few months ago (last iOS release).

 

Windows 10 supports it as well. This is not so important because the most important path for 464XLAT is broadband networks is the CPE.

 

The document I mention before is precisely to ensure that CPEs support it.

 

If you CPE doesn’t, just reflash it with OpenWRT, and you’re done!


Regards,

Jordi

 

 

 

De: Mark Tinka <mark.tinka at seacom.mu>
Fecha: lunes, 3 de diciembre de 2018, 10:15
Para: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>, Diarmuid O Briain <diarmuid at obriain.com>, UIXP Techies <techies at uixp.co.ug>, <afnog at afnog.org>
Asunto: Re: [afnog] IPv6 transition mechanism used by ISP

 

 

On 3/Dec/18 11:06, JORDI PALET MARTINEZ wrote:

I will strongly suggest not going to “only” NAT64/DNS64, but instead using 464XLAT, and even not using DNS64 in that case.

 

If you just use NAT64/DNS64, you have the problems you mention when some apps use literals, old APIs, etc, and you may break DNSSEC. Those problems vanish with 464XLAT.


Agreed.

It has been a while since I tested our rig, but back then, 464XLAT support was very poor, both in phones and CPE.

I haven't checked the current state-of-the-art, if I'm honest. Do you have a summary of where things are?

Mark.





**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.afnog.org/pipermail/afnog/attachments/20181203/a4bf78b5/attachment-0001.html>


More information about the afnog mailing list