Carl Lowenstein said:
>
> 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.
>
This seems very much like the problem I was having on cox when my
modem started failing. No one could give me reproducable test but,
after I replaced the modem it stopped happening.
--
Neil Schneider pacneil_at_linuxgeek_dot_net
http://www.paccomp.com
Key fingerprint = 67F0 E493 FCC0 0A8C 769B 8209 32D7 1DB1 8460 C47D
Secrecy, being an instrument of conspiracy, ought never to be the
system of a regular government.
- Jeremy Bentham, jurist and philosopher (1748-1832)
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
