<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Ever since the Nachi virus hit... in </title>
<link>http://www.dslreports.com/forum/r14131450</link>
<description></description>
<language>en</language>
<pubDate>Mon, 30 Nov 2009 20:41:51 EDT</pubDate>
<lastBuildDate>Mon, 30 Nov 2009 20:41:51 EDT</lastBuildDate>

<item>
<title>Ever since the Nachi virus hit...</title>
<link>http://www.dslreports.com/forum/remark,14131450</link>
<description><![CDATA[<A HREF="/useremail/u/739779"><b>gheezer</b></A> : Which caused so much damage using the ICMP protocol....networks around the world have taken to applying rate limits and filters on ICMP traffic at the edge of their networks. Simple ping usually works ok, but long streams of ICMP often triggers the filtering rules and can lead to erroneous data.<br><br>Maybe a small packet UDP tool wouldn't be subject to such filtering and rate limiting, but as long as ICMP is used, there will be situations where the resultant output is erroneous and possibly misleading.<br><br> TKJunkMail <A HREF="/useremail/u/594412"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>, the kid on the phone probably doesn't HAVE direct access to the network and therefore is incapable of correctly diagnosing a core network issue, and they would DEFINATELY not be allowed to configure, modify, or re-engineer said network. The Kid on the phone usually does have some tools at his/her disposal to advise callers that there are known issues. beyond that, helping the caller with their own PC is about the extent of their capability. I say cut the kid some slack..he/she's doing the best they can.<br><SMALL>--<br>Join the NAVY, see the world....It's mostly water!</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,14131450</guid>
<pubDate>Sun, 14 Aug 2005 11:26:32 EDT</pubDate>
</item>

</channel>
</rss>
