site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
235
Share Topic
Post a:
Post a:
AuthorAll Replies


MxxCon

join:1999-11-19
Brooklyn, NY

1 edit

Credit where Credit is due

why Robb Topolski always gets the credit for detecting spoofed RST packets on Comcast when i detected it more than 3 years earlier on OOL »Re: Why Is OOL Selectively Blocking Bit Torrent Pa

I even contacted all the major bittorrent developers to work out a solution
»Good news
»more good news for us
»Re: Why Is OOL Selectively Blocking Bit Torrent Pa



Give credit where credit is due
--
Check out my awesome city of MxxTopia »mxxtopia.myminicity.com/ind or »mxxtopia.myminicity.com (the more people visit, the bigger it is)

BubbaDude

join:2008-06-06
Livermore, CA

I'll gladly give you credit, but I'd have to know your name.



funchords
Hello
Premium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5

3 edits

reply to MxxCon

said by MxxCon:

why Robb Topolski always gets the credit for detecting spoofed RST packets on Comcast when i detected it more than 3 years earlier on OOL »Re: Why Is OOL Selectively Blocking Bit Torrent Pa
Great job!

There were some other reports here and there, but yours is great because it connected the RST to a particular sequence.

You deserve credit for that. That Cox thread at the top of the thread is a good one, too. That one is a new one on me -- I'd never seen that one before.

said by MxxCon:

I even contacted all the major bittorrent developers to work out a solution
»Good news
»more good news for us
»Re: Why Is OOL Selectively Blocking Bit Torrent Pa



Give credit where credit is due
And it's all yours. I did see some others but nobody that had ruled out the distant-end ISP or attributed it to a specific tool. I'm not sure I read your original report before, but your report is especially good. I also wasn't the first one to notice some odd behavior on Comcast that now -- in retrospect, we can say was probably Sandvine. If I didn't figure this out, eventually someone else would have. I was just the first (that I know of) that put it all together involving Comcast/Sandvine and (like you did) the protocol specifics.

I also approached the situation in a similar way as you, with just a few differences. Further, the biggest difference -- the explosive blog/press coverage and Comcast's PR and legal hijinx -- I had nothing to do with. That controversy is what gave the story some real legs.

I was the first to attribute RSTs to Comcast using Sandvine with the sequence being the injected packet right after the distant peer requested file data (ED2K/BitTorrent). (Like you, I also saw it after the BitTorrent bitfield.)

I also tested end-to-end capturing both sides, and I also tested on a different ISP under exactly the same conditions and showed it didn't happen. I also used my real name (which I've always done).

But that didn't make much difference at first. Like yours, when I reported mine, it didn't garner a lot of attention.

I'm really not responsible for what happened next. Three months later, the blogosphere suddenly picked it up (#2 story on Digg that week), then the mainstream press. And even with that, the issue probably would have eventually died if Comcast wasn't such a PR idiot about it.

What's important is that it was fully exposed and it's stopping.

Very good job finding it on OOL. You did a good job and it's cool that you worked with Azureus to work around it. Is it still going on when you're not using lazy bitfield or other obfuscation?
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More features, more fun, Join BroadbandReports.com, it's free...


MxxCon

join:1999-11-19
Brooklyn, NY

I have nothing against you Robb. The publicity you brought to this issue is undeniable.
However, whenever throttling/net neutrality topic comes up, Karl always mentions you as a the 1st documented proof of ISPs messing with the network. I pointed it out to Karl a few times that ISPs have been doing it for alot longer and Comcast wasn't the 1st, but it's fallen on deaf ears.

I don't use my real name because I don't want some of the stupid things i say online to affect me in RL(also similar to the issue i brought up in »Privacy in OOL Direct forum?).



funchords
Hello
Premium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5

said by MxxCon:

I don't use my real name because I don't want some of the stupid things i say online to affect me in RL(also similar to the issue i brought up in »Privacy in OOL Direct forum?).
I know what you mean, I stopped using Comcast for this very same retaliation. They didn't like what I was saying, and attacked me personally -- »Complain about Comcast=Have your Reputation Scrutinized -- regardless of the fact that everything I said was repeatedly and independently shown to be true many months earlier.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon
More features, more fun, Join BroadbandReports.com, it's free...

Thursday, 31-May 07:02:12 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics