On 11/4/05, Juan M. Duran <[EMAIL PROTECTED]> wrote:
> On vie, 2005-11-04 at 17:22 -0800, Carl Lowenstein wrote:
>
> > My best diagnostic tool is a running Azureus bit-torrent client, with
> > its graphic display of transfer rate vs. time.
>
> Maybe if you have a lot of hosts, this saturates the dynamic MAC table
> of the router.
>
> This effect can even happen without Azureus/emule/whateverP2P running,
> because if you are a habitual user of those programs, even if you close
> the program, clients will try to connect to you after several hours
> (even days).
By the way, I forgot to mention that these 30- to 60-second dropouts
sometimes occur as frequently as two or three in a 15-minute period.
Sometimes not at all over a few hours.
I need a better monitoring program that is independent of Azureus. I
have written a shell script that pings the RoadRunner gateway every
few seconds and reports only when the success/failure status of the
ping changes. But it needs more attention to the effective time
constants of the problem.
Interesting thought -- I might be causing my own problems. Certainly
there can be transactions with on the order of a hundred different
hosts all going on. But saturating the MAC table of the router
doesn't seem like the sort of thing that would cure itself after a
minute or so of inactivity.
The usual cure is to go to the internal webpage of the cable modem
< 192.168.100.1/config.html > and click on "restart cable modem". I
don't see how this would affect the internal state of the router.
Very infrequently (once every few weeks) the router does get locked up
such that it requires a power cycle to recover.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
