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

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

<channel>
<title>Topic &#x27;Re: [Patriot] tracert broken?&#x27; in forum &#x27;RCN&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8767207</link>
<description></description>
<language>en</language>
<pubDate>Fri, 25 Mar 2022 16:16:03 EDT</pubDate>
<lastBuildDate>Fri, 25 Mar 2022 16:16:03 EDT</lastBuildDate>

<item>
<title>Re: [Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8800966</link>
<description><![CDATA[xyzzy42 posted : NicksName, thank you for the explanation.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8800966</guid>
<pubDate>Tue, 16 Dec 2003 07:32:26 EDT</pubDate>
</item>
<item>
<title>Re: [Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8799607</link>
<description><![CDATA[NicksName posted : This is most likely a filter that is in place to prevent the spread of the Nachi/Welchia worm.... Here is an excerpt explanation....<br><PRE><br>The Nachi worm detects the availability of a node by<br>sending ICMP type 8 (echo request) packets before trying<br>to exploit the RPC vulnerability. The size of the ICMP<br>packet is 92 bytes including the IP header. <br> <br>The following Policy Based Routing (PBR) configuration can<br>be used to match and drop the ICMP type 8 and type <br>packets that are 92 bytes long. <br> <br>The ICMP type 8 packets generated by the ping utility on<br>other operating systems such as Cisco IOS, Windows 2000,<br>Linux and Solaris, have different packet sizes than 92<br>bytes. This configuration should not filter the packets<br>that are generated by the ping utility on those operating<br>systems<br>Warning: Microsoft Windows tracert utility uses 92 bytes<br>sized ICMP packets. Using PBR to filter those packets will<br>cause tracert utility not to work.<br></PRE><br>Such a restriction in your aread are likely necessary at the current time in order to prevent Nachi from spreading further.  You should still be able to run traceroute if you run Linux or a non MS windows OS.  <br><br>Or you can download a third party traceroute utility which has a configurable packet size, or one that simply doesn't use 92 byte icmp packets.  It appears that the freeware version of ping plotter available at &raquo;<A HREF="http://www.pingplotter.com/downloads/pngplt_1.exe" >www.pingplotter.com/down &middot;&middot;&middot; lt_1.exe</A> might meet your needs. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8799607</guid>
<pubDate>Tue, 16 Dec 2003 00:33:25 EDT</pubDate>
</item>
<item>
<title>Re: [Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8793263</link>
<description><![CDATA[FLea973 posted : I hope that isn't the case - still haven't heard back yet on the ticket they opened - but the network guy made it sound as if tracert disabled was NOT normal.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8793263</guid>
<pubDate>Mon, 15 Dec 2003 14:04:33 EDT</pubDate>
</item>
<item>
<title>Re: [Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8792364</link>
<description><![CDATA[xyzzy42 posted : This is the reply I received from Patriot Media "support".  What an incredible load of cr@p!<br><BLOCKQUOTE><br>Hello,<br>This is normal...tracert is disabled for network safety<br>Thanks<br>Patriot Support<br></BLOCKQUOTE> ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8792364</guid>
<pubDate>Mon, 15 Dec 2003 12:21:24 EDT</pubDate>
</item>
<item>
<title>Re: [Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8778266</link>
<description><![CDATA[FLea973 posted : I noticed this problem last week too, thought it might be something on my end but didn't have time to check.  It still doesn't work.<br><br>Called Patmedia, (hold time 10m32s after prompts- I thought these were supposed to be faster now)  The rep said it sounds like "a software issue" and was about to dump the call so I quickly explained that 1) Tracert is a network troubleshooting tool that I use to avoid calling them when I can determine network problems I see are not THEIR fault and 2) Tracert is a tool that is probably older than she was, so I sincerely doubt it was the problem.<br><br>I got put on hold and eventually transferred to either tier2 or network support, who ask a little history, said it was odd, I mentioned that you had the same problem in Neshanic Station (so hopefully they look at that too), he did confirm that others using patmedia CAN tracert so it wasn't a global problem, and that Neshanic Sta. and Harding (my loc) are on different UBRs so it wasn't confined to just my area.  He thinks it may be possible that tracert might be accidentally cut off for us and said he has opened a ticket to have them take a look.<br><br>Like ping, tracert isn't something I use a lot, but when I use it, I expect it to work.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Patriot-tracert-broken-8778266</guid>
<pubDate>Sat, 13 Dec 2003 20:46:14 EDT</pubDate>
</item>
<item>
<title>[Patriot] tracert broken?</title>
<link>http://www.dslreports.com/forum/Patriot-tracert-broken-8767207</link>
<description><![CDATA[xyzzy42 posted : I just noticed that all tracert requests are dying one hop past my local system.  Normal pings work normally.  Is anyone else noticing this behavior?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Patriot-tracert-broken-8767207</guid>
<pubDate>Fri, 12 Dec 2003 16:27:53 EDT</pubDate>
</item>
</channel>
</rss>
