Comcast Intercepts and Redirects Port 53 Traffic(tech.slashdot.org)

tech.slashdot.org

Comcast Intercepts and Redirects Port 53 Traffic

http://tech.slashdot.org/story/09/06/09/1731238/Comcast-Intercepts-and-Redirects-Port-53-Traffic?from=rss

9 comments

After 439 comments on Slashdot, and not a single person being able to replicate the results here or on slashdot, I think it's time to kill this story as inaccurate.

Edit: even the original author of the article is claiming "it doesn't happen anymore." It's probably an issue with his testing/setup rather than comcast.

gasull17 anni fa

I agree, but I can't delete the story anymore (there's no link).

ScottWhigham17 anni fa

I hadn't seen the Netalyzer before - damn impressive. Among the impressive results was a "Minor aberration: Your computer's clock is 17ms too fast."

tlrobinson17 anni fa

Can anyone actually reproduce this? According to numerous comments on the /. article (including one from a Comcast representative) this is not true.

obvioustroll17 anni fa

I'm a comcast customer who uses opendns, and I could not reproduce this behavior.

eli17 anni fa

Netalyzer gave a message about port 53, but I'm clearly still using openDNS, so I dunno.

spectre17 anni fa

People believed it because it sounds like something Comcast would actually do.

jmtame17 anni fa

I got this: Direct UDP access to remote DNS servers (port 53) is allowed.

TrevorJ17 anni fa

I read through a lot of the comments on this story, and it appears that it's been problematic to replicate.