DI 624 revC- severe wireless latency after consistent throughput

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

In <(E-Mail Removed). com> on 28 Sep 2005
10:46:50 -0700, (E-Mail Removed) wrote:

>>What's unique about BitTorrent is that it opens up as many parallel
>>streams as it can to move its traffic. My guess(tm) is that the
>>DI-624 can only handle about 32 streams before it complains.

Mine (DI-624 Ver C1 with 2.70 firmware) is currently running with well over
100 open connections.

>>BitTorrent might be trying to open more. If you're running it
>>"unchoked", it can easily open more, especially on a high bandwidth
>>connection. There are some clues here:
>> http://groups.yahoo.com/group/the_gdf/message/21143
>>but I won't pretent to understand all the BitTorrent unique buzzwords.
>>If there's a setting to reduce the number streams, connections, users,
>>or such, you might want to try it. My guess(tm) is that your game
>>might also be trying to do the same thing.
>
>That might be it. It's worth a shot at this point. I'll check to see if
>I can control the number of streams.

Azureus is an excellent BitTorrent client where it's easy to configure the
number of connections, both per torrent, and for all torrents.

--
Best regards, HELP FOR CINGULAR GSM & SONY ERICSSON PHONES:
John Navas <http://navasgrp.home.att.net/#Cingular>

[POSTED TO alt.internet.wireless - REPLY ON USENET PLEASE]

In <(E-Mail Removed)> on Tue, 27 Sep 2005 23:11:35
GMT, Jeff Liebermann <(E-Mail Removed)> wrote:

>On Tue, 27 Sep 2005 22:38:24 GMT, Jeff Liebermann
><(E-Mail Removed)> wrote:
>
>>>I'm pretty
>>>sure it's something to do with DNS caching on the router as enabling
>>>the DNS relay on the router speeds up that process as well. But I can
>>>specify the DNS servers directly through the connection and I don't
>>>have to bother resetting the router for a couple months.
>>
>>Well, that's really odd because DNS timeouts are usually around 30-45
>>seconds and not in milliseconds. Windoze clients also cache DNS
>>lookups for about 24 hours for a successful lookup and 5 minutes for a
>>failed lookup:
>> http://vlaurie.com/computers2/Articles/dnscache.htm
>>If that has an effect, I'm lost. I don't have a clue why the DNS
>>cache would affect ping latency, especially since you're pinging by IP
>>address which does not require a DNS lookup.
>
>Ooops. I forgot that some versions of ping *DO* run a DNS lookup for
>every last lousy ping packet. For ping by IP address, it does a
>reverse DNS lookup. I know SCO Unix OSR5 and the BIND derived
>utilities do that. If the DNS lookup from the cache in the DI-624 is
>delayed, so will the ping results. If the system is really screwed
>and DNS has to go to the root domain servers to walk down the tree to
>the authoritative servers each time, then it would easily take the
>70msecs you've observed. However, methinks that's unlikely.
>
>I'm not sure if Windoze ping also does a DNS/RDNS lookup, ...

Not unless you specify the -a option.

--
Best regards, HELP FOR CINGULAR GSM & SONY ERICSSON PHONES:
John Navas <http://navasgrp.home.att.net/#Cingular>