<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">The original theory (this was out of Cisco’s deployment guide, which now, having learnt a bit more, I realise was talking nonsense) had to do with clients disconnecting and reconnecting and override of old
entries.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">One thing we are finding (and thanks to Jan who pointed this out to me as well), is that Dynamic V6 on the mass market creates problems.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Particularly if you are doing a DHCPv6-PD and then grabbing a segment of the PD to assign to the LAN interface which in turn does RA. Because if the client reconnects and gets a new DHCPv6-PD segment, and
the RA then changes towards the client, the client ends up with two v6 subnets and two gateways until the RA expires, and this breaks things on a number of platforms. (And also ends up with certain large content providers seeing breakage and blacklisting recursives
as a result lol)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The general consensus that I’m seeing elsewhere is that when doing v6 to the mass market, static is better and full of far less problems, and that’s what we’re switching to now with a provisioning system,
so v6 prefix to every client will be static.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Mark Tinka <mark.tinka@seacom.mu><br>
<b>Date: </b>Sunday, 14 August 2016 at 3:49 PM<br>
<b>To: </b>Andrew Alston <Andrew.Alston@liquidtelecom.com>, "afnog@afnog.org" <afnog@afnog.org><br>
<b>Subject: </b>Re: [afnog] A heads up on a nasty IPv6 bug<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:Tahoma"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:Tahoma">On 14/Aug/16 12:09, Andrew Alston wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:1.5pt;margin-top:6.0pt;margin-right:1.5pt;margin-bottom:6.0pt;color:null !important">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt">Hi Guys,</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt">Figured I’d share this because someone might run into the issue I did last night and after how long it took to figure out what was going on, rather give people a heads up.</span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt">Under Cisco IOS-XR 5.3.3 AND under 6.0.2 (though the documentation on the bug explicitly states its fixed in 6.0.2, its NOT), do not, under any circumstances, run ipv6 nd router-preference
high anywhere.</span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="background:white"><span style="font-family:Tahoma"><br>
That's a nasty bug.<br>
<br>
I've only ran ND Router Preference in LAN scenarios, to avoid situations where Windows Vista and Windows 7 clients automatically enabled 6-to-4, and claimed to be the authoritative default gateway for the LAN.<br>
<br>
The solution ended up being pointless as there was no way to fully guarantee that the true router was the one with the highest preference for the LAN.<br>
<br>
The ultimate solution for this is RA Guard, which I believe now has reasonable support on decent Ethernet switches in the wild.<br>
<br>
I'm curious, though, why you'd need this on a point-to-point link, where the remote side (CPE) may not be setup to announce ND RA's back to the BNG.<br>
<br>
Mark.<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>