On Monday 03 December 2007, Allen Weiner wrote: > I just did a quick Google search on "Westell 6100" and Fedora. Nothing > popped out other than my own posts to several forums. What Google search > terms did you use? (Some of my posts were under the nickname AlFrugal).
Just looked for "Westell 6100-E90". The other person I saw having trouble was indeed AlFrugal -- I didn't know that was you. > > Four pages of back-n-forth posts here: > > http://www.webservertalk.com/message2132448.html > > Yes, I had two long threads on comp.os.linux.networking, mostly with > "Bit Twister". He was helpful at first, but the interchange > deteriorated. Ultimately, he insisted that I change my "hosts" file. > Both I and another poster felt the change was unnecessary. I saw that, donno what to make of it. There is one interesting related thing I've tested, though. Anything trying to make any use of the name 'localhost' will fail unless there's an entry for it in /etc/hosts. I can't make any kind of solid argument that this entry is required, but I vaguely remember having a couple of issues when I didn't have that entry -- I just don't remember what they were. :-/ > > Seems like you've been working at this problem for a while. :-/ > > I've been working on this for several months. It's an interesting > learning experience, but the problem is irritating. I initially thought > the problem was loss of DSL sync, but have since concluded that it > isn't. Yeah, I considered that, but for whatever reason this sounds like it's an issue only on a box connected to the router, not the router loosing it's connection. > > Mainly the debugging "hooks" I assume you mean would be 'echo' > > statements before commands to give some text output of what's about to be > > run so that you know what command hangs. That's not that hard. Unless > > you mean something else? > > Yes, I meant putting "echo" statements in the scripts. In one of the > above mentioned threads, "Bit Twister" leads me to think this is not so > easy for a novice like me. I think all he was saying was that the network scripts themselves call other scripts, so in order to get the required verbosity of echo messages it's required to edit several scripts to add echo lines. In the first pass you'll only need to edit /one/ script to add echo lines at which you might find that the command that is hanging is a script; then you'll go edit that script to add echos, and you might find that what hangs is a script. Etc. That's at least what it sounded like. I think he made it sound harder than it really is; why it was so hard for him was that he tried to add echo lines to ALL of the files at the same time, right off the bat, which really isn't necessary. Just make backups of the files before editing them and make notes of which files you changed so you can change them back if needed. > > You might want to compare the output of 'iptables -L -n' before + > > after the problem; Tauno Voipio indicated that the router was trying to > > connecto to your local box on port 80, which is something very unusual, > > and he was concerned that your local Fedora 7 firewall would dynamically > > make rules to block out the router. > > The conclusion I reached from Tauno Voipio's comments is that every 15 > seconds, Verizon is probing my modem/router to see if I'm running a > server. Hmm. That's rather annoying. Seems pointless to check every 15 seconds. > My daily logwatch report always shows many megabytes worth of > packets flagged by iptables. I'd like to check on the Verizon forums of > dslreports.com to see if others observe this happening to them. I hope the logwatch package has regex filters you can make for it to eliminate known "okay" issues, similar to logcheck, so that you don't get spammed from your own system. > I'll look into your suggestion re issuing the iptables command. I didn't > pursue that angle any further previously because the problem doesn't > occur following a reboot, even though I'm typically on for many > additional hours. One of the other suggestions I remember reading had to do with the lease time. I think the idea was to figure out if the lease time was about two hours (I.E. 7200 seconds). Have a look at the files in /var/lib/dhcp3/ and see if those exist and what the dhcp-lease-time in them is. If it just happens to be 7200, that would be overly coincidental. -- Chris -- Chris Knadle [EMAIL PROTECTED] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Dec 5 - Open Source Show and Tell Jan 2 - TBD Feb 6 - DBUS Mar 5 - Setting up a platform-independent home/small office network using Linux
