<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: AT&#038;T Internet Outage in Bay Area Disrupts Internet Traffic</title>
	<atom:link href="http://www.theinternetpatrol.com/att-internet-outage-in-bay-area-disrupts-internet-traffic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theinternetpatrol.com/att-internet-outage-in-bay-area-disrupts-internet-traffic/</link>
	<description>Internet Safety, Windows Updates, Internet News, and More</description>
	<pubDate>Sat, 21 Nov 2009 20:42:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Bill Cole</title>
		<link>http://www.theinternetpatrol.com/att-internet-outage-in-bay-area-disrupts-internet-traffic/#comment-41254</link>
		<dc:creator>Bill Cole</dc:creator>
		<pubDate>Wed, 07 Feb 2007 16:43:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.theinternetpatrol.com/?p=1492#comment-41254</guid>
		<description>Just a side-note on the '*' in traceroute output. It doesn't necessarily mean that there is nothing there, it can mean that a router (or a string of them) in the path are either configured intentionally to not respond to traceroute's probe packets or are responding in a fashion that some other machine in the return path is seeing as bogus. An example of the latter would be the use of private addresses in routers in a way that causes their ICMP responses to be sent with source addresses in a RFC1918 network that some other routers and firewalls reasonably consider bogus and drop-worthy. 

In the end, it is not definitive that packets are traveling off into nowhere just because traceroute trails off into asterisks.</description>
		<content:encoded><![CDATA[<p>Just a side-note on the &#8216;*&#8217; in traceroute output. It doesn&#8217;t necessarily mean that there is nothing there, it can mean that a router (or a string of them) in the path are either configured intentionally to not respond to traceroute&#8217;s probe packets or are responding in a fashion that some other machine in the return path is seeing as bogus. An example of the latter would be the use of private addresses in routers in a way that causes their ICMP responses to be sent with source addresses in a RFC1918 network that some other routers and firewalls reasonably consider bogus and drop-worthy. </p>
<p>In the end, it is not definitive that packets are traveling off into nowhere just because traceroute trails off into asterisks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
