2connections for each logical con to prevent packetshapers?

Technical discussion about the NMDC and <a href="http://dcpp.net/ADC.html">ADC</A> protocol. The NMDC protocol is documented in the <a href="http://dcpp.net/wiki/">Wiki</a>, so feel free to refer to it.

Moderator: Moderators

Posts: 1
Joined: 2004-09-25 12:43

2connections for each logical con to prevent packetshapers?

Post by wolf5 » 2005-01-08 19:03

Would it be a good idea to create 2 connections when sending filedata between clients?

Today the ISP using packetshapers will easily sniff out a string to identify the current connection as a DC++ data transfer connection, and thereby throttling it.

If instead of using 1 connection in DC++ someone implement the use of a second connection. The first connection will contain the control data - the data that the sniffers will identify as DC data. The second connection will contain the raw file data.

That way - even if the control data connection gets throttled to a very low bandwith - the actual data will still flow through pretty quickly as there isnt much control data needed ( i believe? ).

As my ISP has added some sort of packetshaper hardware on my outgoing DC traffic I'm pretty eager to get something like this implemented. But there is no use for me to code this unless it get's public as both clients that connects needs to know the new way to send data.

Any thoughts on this? A feeble idea or a breakthrough vs packetshaper tech?

DC++ Contributor
Posts: 3212
Joined: 2003-01-07 21:46
Location: .pa.us

Post by GargoyleMT » 2005-01-12 13:01

ADC connections may be SSL encrypted before too long. Using two connections is just playing a very small game of leapfrog - after all, FTP also uses two channels, and is handled by existing packet shaping solutions.

So, if you want to contribute, take a look at the ADC draft and the CVS version of DC++.