<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(0, 0,
0); font-family: Tahoma; font-size: 16px;" bgcolor="#FFFFFF"
text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 15/Aug/16 11:51, Mukom Akong T.
wrote:<br>
<br>
</div>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: null !important; color:
null !important;"
cite="mid:1DC3DD363C6F708B.AF85B957-E328-4AE7-96A5-DE58980D3135@mail.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div id="compose" style="padding-left: 20px; padding-right: 20px;
padding-bottom: 8px;" contenteditable="true">Very succulent
description. It still doesn't explain why host behind CPE gets
two different default gateways as Andrew is reporting. </div>
<div id="compose" style="padding-left: 20px; padding-right: 20px;
padding-bottom: 8px;" contenteditable="true">Unless in reality,
between provisioning the various LAN-side /64s (or some other
yet to be identified event), the link local address of the LAN
interface changes. </div>
<div id="compose" style="padding-left: 20px; padding-right: 20px;
padding-bottom: 8px;" contenteditable="true"><br>
</div>
<div id="compose" style="padding-left: 20px; padding-right: 20px;
padding-bottom: 8px;" contenteditable="true">Static Prefix will
fix the problem of reachability due to an no-longer valid
prefix. The different default gateways issue will still be
present. Right?</div>
</blockquote>
<br>
To me, sounds like a code implementation issue in the CPE and/or
client.<br>
<br>
Mark.<br>
</body>
</html>