<div dir="ltr">Congrats to you Andrew & Liquid for paving the way!<div><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 August 2016 at 10:32, Andrew Alston <span dir="ltr"><<a href="mailto:Andrew.Alston@liquidtelecom.com" target="_blank">Andrew.Alston@liquidtelecom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><br></p>
<p class="MsoNormal"><br></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">The next issue was, enabling the SLAAC to the customer (since that only works on /64s), and to do this, we’re pushing config to the CPE’s that takes a /64 out of the /48 that’s routed and automagically puts it
on the LAN interface with SLAAC enabled. This works perfectly with the CPE’s we are using, and we’re testing it with other CPE’s to have more variety of choice of CPE as well.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Sadly, the CPE’s we’ve seen did NOT do this straight out of the box so we have to push a config on installation when a new customer connects.</span></p></div></div></blockquote><div><br></div><div><br></div><div>Not just that, there's no standardised way of dealing with these "Delegated prefixes". This capability (automatically request a delegated prefix, then automatically pick /64 from them and push them out LAN interfaces via SLAAC or DHCP) should be a mandatory requirement when an ISP is procuring CPEs for IPv6 deployment</div><div><br></div><div>We do cover this scenario both theory and labs during our training workshops.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><span style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">The next biggest issue was customers who for some bizarre reason wanted to run CPE’s behind the CPE’s supplied (effectively doing dual-NAT on the v4), and if those don’t support v6 or aren’t configured for it,
there isn’t a huge amount we can do.</span></p></div></div></blockquote><div><br></div><div><br></div><div>I'd be curious to know why they are doing that. When I've tried that, it's always been because i wanted to plug and use my own more powerful CPE with IPv6 capability (instead of the crappy one ISPs tend to provide) </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><span style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">With regards to actual machines picking up the v6 where the above scenario isn’t happening, zero problems, and we’re actively seeing a large number of V6 DNS requests to our DNS servers coming from the customers
and we’ve seen a massive increase in our V6 traffic levels since enabling this – so we know for a fact customers are actually using the v6 in fairly large volumes. In particular I see a LOT of v6 to Google, Facebook, Amazon AWS, and various other sites.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">So far so good though, but we’re constantly monitoring and hopefully in the next few weeks once we have collected a lot more statistics I’ll be able to share those as well.</span></p></div></div></blockquote><div><br></div><div><br></div><div>Kudos once again!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" lang="EN-GB" link="#0563C1" vlink="#954F72"><div><p class="MsoNormal"><span style="color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Andrew<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Mark Tinka [mailto:<a href="mailto:mark.tinka@seacom.mu" target="_blank">mark.tinka@seacom.mu</a>]
<br>
<b>Sent:</b> 12 August 2016 13:07<br>
<b>To:</b> Andrew Alston <<a href="mailto:Andrew.Alston@liquidtelecom.com" target="_blank">Andrew.Alston@liquidtelecom.<wbr>com</a>>; <a href="mailto:afnog@afnog.org" target="_blank">afnog@afnog.org</a><br>
<b>Subject:</b> Re: [afnog] IPv6 Native Mass Market Deployment arrives in Kenya!<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif">Hi Andrew.<br>
<br>
Many congratulations. This is, indeed, a major step, and for me, the first of its kind in eastern and southern Africa (mostly because I'm not sure how far this is going in northern and western Africa - otherwise I'd say the whole of Africa).<br>
<br>
I've been challenging a number of broadband ISP's and MNO's in Africa in recent years to put a lot more focus and energy in getting consumers IPv6-enabled, so to hear that Liquid have succeeded in doing this in Kenya is very good news, indeed!<br>
<br>
It would be good to hear of challenges specifically around customer devices picking up IPv6 addresses, and potentially running into Happy Eyeball issues if at all. If you can share that as your experience grows, it would tell a good story.<br>
<br>
Once again, good work, Andrew and your team! I'm quite impressed to hear this!<br>
<br>
Mark.</span><span style="font-size:12.0pt;font-family:"Tahoma",sans-serif"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">On 12/Aug/16 11:45, Andrew Alston wrote:<u></u><u></u></span></p>
</div>
<blockquote style="margin-left:1.5pt;margin-top:6.0pt;margin-right:1.5pt;margin-bottom:6.0pt;background-color:null!important;color:null!important">
<p class="MsoNormal">Hi All,<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">I thought I’d just share this with all of you because I view it as a fairly major step in the right direction for the continent.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Yesterday, Liquid Telecom turned on IPv6 to all its Kenyan home users using GPON and our FTTH / FTTB products. This was done in such a way that the customers didn’t need to configure anything themselves to enable it, it was just there
<span style="font-family:Wingdings">J</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">The CPE’s are all pushed a configuration as well to SLAAC enable the LAN facing interface and doing v6 DNS distribution via ND (though we also have v6 DHCP serving V6 DNS and other-config-flag set on the ND, so it can get the v6 DNS via
either method if it doesn’t honor the other-config-flag)<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Though, this is now a challenge to all the other ISP’s offering home user mass market products – v6 works – it’s time to start seeing more deployment
<span style="font-family:Wingdings">J</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">We hope to have the v6 turned up shortly in Zimbabwe and other markets in the next few weeks as well.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Andrew<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Tahoma",sans-serif"><u></u> <u></u></span></p>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
afnog mailing list<br>
<a href="https://www.afnog.org/mailman/listinfo/afnog" rel="noreferrer" target="_blank">https://www.afnog.org/mailman/<wbr>listinfo/afnog</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br>Mukom Akong T.<br><br><span style="font-family:inherit;font-style:inherit;font-variant:inherit;line-height:inherit;color:rgb(51,51,51);margin:0px;padding:0px;border:0px;vertical-align:baseline"><a href="https://www.linkedin.com/in/mukom" target="_blank">LinkedIn:Mukom</a> </span> | twitter: @perfexcellent <div style="margin:0px;padding:0px;border:0px;font-family:Helvetica,Arial,sans-serif;vertical-align:baseline;line-height:17px;color:rgb(51,51,51)"><form action="https://www.linkedin.com/profile/vanity-name-submit" name="UNIQUE_ID_SafeHtmlFilter_vanityUrlForm" method="POST" style="margin:0px;padding:0px;border:0px;font-style:inherit;font-family:inherit;vertical-align:baseline;font-variant:inherit;line-height:inherit" target="_blank" onsubmit="try {return window.confirm("You are submitting information to an external page. \nAre you sure?");} catch (e) {return false;}"><ul style="margin:0px;padding:0px;border:0px;font-style:inherit;font-family:inherit;vertical-align:baseline;list-style:none;font-variant:inherit;line-height:inherit"></ul></form></div>------------------------------------------------------------------------------------------------------------------------------------------<br>“When you work, you are the FLUTE through whose lungs the whispering of the hours turns to MUSIC" - Kahlil Gibran<br>-------------------------------------------------------------------------------------------------------------------------------------------<br></div></div></div>
</div></div></div>