It's impossible to workaround the Comcast (or should I say Sandvine ) technique by only fixing something on your end . Those forged reset packets are going to both participants in the conversation. Because both sides think the other person wants to hang up, the session is permanently discarded. It's then up the application to decide if it wants to initiate a new conversation.
This wouldn't be so obnoxious to the non-bit torrent world if it wasn't also harming other systems, such as Hamachi VPN, Lotus Notes, and sometimes even Google (still can't explain the logic behind that, but there are packet traces to prove it).
Please tell me those economy seats don't use touch-screens. Imagine the fun of someone poking the back of your seat's headreset for 12 hours while they work on their PowerPoint presentation.
There is a way to combat this, but it requires you to enable Window's Data Execution Prevention. At least two of the executable compression packages I played with tout their ability to obscure source code by extracting, and then running purely out of memory. Unfortunately, their compression payload then has to run out of memory marked for data storage. Turn on DEP, and the programs are doa
I read the Avalanche paper and it looked like they were essentially proposing taking a newly shared Bittorent file, generating a sizeable par file, and prepending it onto the real file data before seeding it. The clients just keep checking to see if they have enough blocks downloaded and then reassemble the file.
Slashdot Mirror
It's impossible to workaround the Comcast (or should I say Sandvine ) technique by only fixing something on your end . Those forged reset packets are going to both participants in the conversation. Because both sides think the other person wants to hang up, the session is permanently discarded. It's then up the application to decide if it wants to initiate a new conversation. This wouldn't be so obnoxious to the non-bit torrent world if it wasn't also harming other systems, such as Hamachi VPN, Lotus Notes, and sometimes even Google (still can't explain the logic behind that, but there are packet traces to prove it).
Please tell me those economy seats don't use touch-screens. Imagine the fun of someone poking the back of your seat's headreset for 12 hours while they work on their PowerPoint presentation.
There is a way to combat this, but it requires you to enable Window's Data Execution Prevention. At least two of the executable compression packages I played with tout their ability to obscure source code by extracting, and then running purely out of memory. Unfortunately, their compression payload then has to run out of memory marked for data storage. Turn on DEP, and the programs are doa
So am I missing something?
I read the Avalanche paper and it looked like they were essentially proposing taking a newly shared Bittorent file, generating a sizeable par file, and prepending it onto the real file data before seeding it. The clients just keep checking to see if they have enough blocks downloaded and then reassemble the file.