Script to measure DC-protocol timing?

[Mobe]

Hi,
Rumours are that ISPs limit DC-traffic at their outer limits ie on their connections to exchange points.

Is there a way to measure how long it takes to do client to hub or client to client DC-commands?

Like testing your connection quality with ping and tracert?

If one could measure his connection capabilities on local hub and compare this to a hub that is on another ISP's connection, we would have facts that some limiting occurs for DC-protocol. Since it is allready known that no limiting is used on http or ftp.

So is there such a script or can it be done?
Or client with speedometer?
Or maybe software that emulates client?

Mobe

[bastya_elvtars]

As far as I know, these TCP and UDP packets should be analyzed in order to know they are really DC proto commands. They are simply limiting access to port 411 instead.

[Mobe]

Yes, some ISPs block port 411 and you must use different port to run hub.
But client-client connection does not use port 411.
The DC downloads are slow but FTP between same two users go full speed.

[plop]

Originally posted by Mobe
Yes, some ISPs block port 411 and you must use different port to run hub.
But client-client connection does not use port 411.
The DC downloads are slow but FTP between same two users go full speed.

try putting your clients on port 21.
it's more likely they tell which ports not 2 limit then the other way around.
by putting doing this test you can clearly see if they limit the port or the protocoll.

plop