Well, this is reassuring. For the record, we had a hiccup here in the Roanoke VA area that (probably) hosed the cable modem. I had to power-cycle the modem (and rebooted the Dach firewall) before connectivity was restored. The "muliple modems off-line" problem might be due to flaky head-end equipment, but in the case of this particular hiccup the online light was steady before I cycled it. I will look for that symptom as well, tho. Thx.
Bruce Slade wrote: > I also have the charter service, though not using leaf on it. I have a > linksys plugged into the cable modem. The linksys receives the address > via dhcp, with the linksys serving addresses to my internal network. > I'm out of the Kennewick, WA branch. While not daily by any means (but > very frequently), I have noticed that the charter network seems to fade > away totally out of the blue. When this has happened, I usually try to > ping a known fixed IP down the road a ways, just to see if the charter > dns servers are hosed, or if it is a network connection issue. The > greatest majority of the time it has been a network connection issue > within the charter entity. And when it has gone on for more than a few > minutes I have called it in. When I have been able to contact one of > the good techs, it turns out that they show multiple cable modems off > line, which points them back to something internal on their end. A long > story for which I appologize, but thought I would offer it in view of > the questions and issues Dr. Tibbs refers to. > > From what I have been told by multiple charter techs, they only use dhcp > for home clients. From my experience the "flakiness" is a result of > network connection issues within charter, and not DNS issues. DNS is > usually the first indication of network connectivity issues, but from > this end hasn't been the root cause of the connection problems. When > Dr. Tibbs starts having the DNS issues, watch the lights on the modem, > and you will notice that the modem is really acting spazzy and that the > "online" light will not be on steady. > > Just my 25 cents to hopefully cast a little more light on the subject. > Dachstein isn't the only "firewall" that has issues on charter. > > "Dr. Richard W. Tibbs" wrote: > >>The LAN hosts are configured manually with the DNS servers from Charter. >>Rather not do it this way, but I couldn't seem to get dnscache to serve >>up names. Hope to resolve this with a newer Dachstein or other leaf. >> >>Over 3 million boxes unpacked.... only a few thousand more.... >> >>Brad Fritz wrote: >> >> >>>On Sun, 28 Jul 2002 09:39:48 EDT Dr. Richard W. Tibbs wrote: >>> >>> >>> >>>>The Dachstein >>>>firewall has allowed access more-or-less continuously for several days >>>>now, since the last reboot. The "less" part has been that every so >>>>often it appears that DNS service "goes away", that is hosts become >>>>unreachable. I can still ping the firewall's gateway addr >>>>(192.168.1.254) during these periods. >>>>The lease periods on the cable side of the firewall are 4-hour leases, >>>>and the internal side of the firewall gives IP leases of 12 hours. >>>> >>>> >>> So possible explanations include >>> >>> >>>>1) temporary lease "fumbling" every 4 hours. >>>>2) flaky, overloaded DNS servers at Charter (what a surprise...) >>>> >>>> >>>If you're running DNS cache on the router and the LAN hosts are >>>using it, the answer to #2 is probably no. dnscache should start >>>with the root name servers and work their way down to resolve >>>names. Charter's DNS servers should be bypassed completely unless >>>you're resolving a name for which those DNS servers are >>>authoritative. The exception is if you explicitely configure it >>>to forward all queries or certain domains to Charter's DNS servers. >>>(I've been jumping around in leaf-user postings, so forgive me if >>>you indicated you are using such a setting in an earlier posting.) >>> >>> >>> >>>>Let me pursue a more recent Dachstein (or maybe Bering?) and see if the >>>>problem persists. >>>> >>>> >>>Good idea. >>> >>>--Brad >>> >>> >>> >>>------------------------------------------------------- >>>This sf.net email is sponsored by:ThinkGeek >>>Welcome to geek heaven. >>>http://thinkgeek.com/sf >>>------------------------------------------------------------------------ >>>leaf-user mailing list: [EMAIL PROTECTED] >>>https://lists.sourceforge.net/lists/listinfo/leaf-user >>>SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html >>> >>> >>------------------------------------------------------- >>This sf.net email is sponsored by: Dice - The leading online job board >>for high-tech professionals. Search and apply for tech jobs today! >>http://seeker.dice.com/seeker.epl?rel_code=31 >>------------------------------------------------------------------------ >>leaf-user mailing list: [EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/leaf-user >>SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html >> > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
