On Tue, Oct 28, 2008 at 06:08:51PM +0100, Damian Gerow wrote: > I took a closer look, and found that the problems actually started on Wednesday. > I'm so glad I finally got cacti up and running, now I just need it to start > graphing retransmits and errors as well... Ian! Allen sent me some interesting graphs from a SpeedTouch. He's on NCF/TekSavvy and in my neighbourhood. > > The remote host (first hop) can be 206.248.154.101 or 102, 103, 105, > > or 120, which it is right now. It seems to have cleared up for the most > > part over the weekend, although with all the rain Saturday my connection was > > extremely slow (not much better than dialup) with many many CRC errors > > (an urelated problem?). > > Right now, I'm actually suspecting that the backhaul from Ottawa into Toronto -- > where Bell hands off to TekSavvy -- is overloaded. I'm not 100% confident this > is the case, but it's the most plausible solution I've come across. Too bad your > problem seems to have cleared up, as mine's ongoing. Too bad yours is ongoing. > On what layer were you seeing CRC errors? Were they showing up on the modem, > on your gateway, on the client machines...? On the modem. SpeedTouch, "adsl info". They show up clearly in Ian!'s graphs. > > > However, when connected using Bell's test account, > > > I'm seeing zero packet > > > loss (and, unsurprisingly, slightly better latency). > > > > How does one get one of those? > > I'm not sure how kosher it is > > username: ***** > password: ***** I'll keep this in mind for the next time. > NB: I doubt you'll have access to the Internet with this. Too bad. I could save a few bucks (I'm on a fixed income). :-) Howard E.