<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ICSI Netalyzr &#8211; probing for problems</title>
	<atom:link href="http://www.p2pnet.net/story/23039/feed" rel="self" type="application/rss+xml" />
	<link>http://www.p2pnet.net/story/23039</link>
	<description>p2pnet.net - reader powered</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:11:09 -0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Devil's Advocate</title>
		<link>http://www.p2pnet.net/story/23039/comment-page-1#comment-975780</link>
		<dc:creator>Devil's Advocate</dc:creator>
		<pubDate>Wed, 10 Jun 2009 14:53:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=23039#comment-975780</guid>
		<description>&quot;...user tests using the new Netalyzr tool seem to confirm Comcastâs side of the story...&quot;

I wouldn&#039;t be too quick to dismiss this, just because the Netalyzr tool didn&#039;t see it.

Many savvy users of various networks have been experiencing what seems to amount to a &quot;DNS hijacking&quot; by the providers.  Rogers in Canada seemed to start the ball rolling some time back by inserting their own pages (complete with their advertising) whenever a user would enter an invalid URL.  A few people I know say Rogers is still doing this.

Many have reported that they&#039;re not getting their browsers&#039; error pages in return for a bad URL, they&#039;re getting something with their provider&#039;s name on it.  And some have been complaining they&#039;ve gotten strange search pages that don&#039;t trace back to the mistyped URL in any way.  Indeed, many of the erroneous URLs in question didn&#039;t have a registered forwarding page, and therefore, should not have resolved.

There isn&#039;t a good reason why invalid URLs should resolve, instead of returning the proper &quot;error page&quot; from the browser&#039;s own internal files.  And, providers just may have an interest in fucking with Port 53, as some popular torrent clients direct most of the UDP requests for bittorrent connection discoveries through that port.

Now, I&#039;m not saying everyone needs to immediately put on their tinfoil hat here...
I&#039;m just saying it might not hurt to keep it handy.
Many of the providers out there have been consistently demonstrating they will do pretty much anything to circumvent file sharing.  I&#039;m conditioned not to trust them.  Whether this is another attempt to screw with BT, I can&#039;t answer that right now.

But, I&#039;m going to do what I can to find out!...</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;user tests using the new Netalyzr tool seem to confirm Comcastâs side of the story&#8230;&#8221;</p>
<p>I wouldn&#8217;t be too quick to dismiss this, just because the Netalyzr tool didn&#8217;t see it.</p>
<p>Many savvy users of various networks have been experiencing what seems to amount to a &#8220;DNS hijacking&#8221; by the providers.  Rogers in Canada seemed to start the ball rolling some time back by inserting their own pages (complete with their advertising) whenever a user would enter an invalid URL.  A few people I know say Rogers is still doing this.</p>
<p>Many have reported that they&#8217;re not getting their browsers&#8217; error pages in return for a bad URL, they&#8217;re getting something with their provider&#8217;s name on it.  And some have been complaining they&#8217;ve gotten strange search pages that don&#8217;t trace back to the mistyped URL in any way.  Indeed, many of the erroneous URLs in question didn&#8217;t have a registered forwarding page, and therefore, should not have resolved.</p>
<p>There isn&#8217;t a good reason why invalid URLs should resolve, instead of returning the proper &#8220;error page&#8221; from the browser&#8217;s own internal files.  And, providers just may have an interest in fucking with Port 53, as some popular torrent clients direct most of the UDP requests for bittorrent connection discoveries through that port.</p>
<p>Now, I&#8217;m not saying everyone needs to immediately put on their tinfoil hat here&#8230;<br />
I&#8217;m just saying it might not hurt to keep it handy.<br />
Many of the providers out there have been consistently demonstrating they will do pretty much anything to circumvent file sharing.  I&#8217;m conditioned not to trust them.  Whether this is another attempt to screw with BT, I can&#8217;t answer that right now.</p>
<p>But, I&#8217;m going to do what I can to find out!&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>


