<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/09/2014 1:55 PM, Beeson, Ayden
wrote:<br>
</div>
<blockquote
cite="mid:DDA93F19FCAF1E408E16C64697F74B26D4DFE5237E@MAIL01.CSUMain.csu.edu.au"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">I’ll
have another look at actual router level access from the WAN
but I’d still see it in my netflow collection from that
interface.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">I’m
99.99% percent it isn’t coming from me or even to me
directly, I thought the same as you and did a lot of digging
to double check.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US">I
have both SNMP and Netflow monitoring and logging configured
on the modem and neither show any significant activity
during these time periods on either the up or the
downstream. </span></p>
</div>
</blockquote>
It may be a re-training bug between your modem and the DSLAM. ADSL2+
is supposed to re-train to a new sync rate seamlessly without packet
drops, whereas the older ADSL1 had to effectively drop the line,
re-sync, generate a new bitfield table per tone to cope with changes
to background noise and cross-talk that caused a need for a re-sync.
<br>
Perhaps there is a bug causing the DSLAM and the modem to become
confused about the number of bits per tone, and which bits go in
which DSL tone, on the transmission path. That would cause a very
high bit-error-rate, causing packets to be dropped when checksums
and fields come through corrupted.<br>
<br>
Have you tried a different make/model DSL modem?<br>
<br>
P.<br>
<br>
</body>
</html>