On Monday 03 December 2007, Allen Weiner wrote: > I run Fedora 7 on my desktop PC and use Verizon DSL. My modem is a > Westell 6100-E90 modem/router.
When using Google to look up the router, I see that other Fedora 7 users are having trouble, and that you've posted this query elsewhere. Four pages of back-n-forth posts here: http://www.webservertalk.com/message2132448.html Two more pages of troubleshooting posts here: http://fixunix.com/networking/11810-difficulty-recovering-dsl-loss-sync.html Seems like you've been working at this problem for a while. :-/ > I'd like to pinpoint where "service network restart" hangs. How can I do > this? > > Two approaches come to mind: > > 1. Place hooks in the networking scripts that are invoked by "service > network restart". This approach is unappealing to me. I have no > experience with BASH scripting. (Although I could keep backups of the > original scripts.) It's time for you to get used to Bash. Print a copy of the "Advanced Bash Scripting Guide" and read it. http://tldp.org/LDP/abs/abs-guide.pdf Some distributions have a package for this manual, such as the package 'abs-guide' on Debian; there might be a similar package for Fedora so you could look at the guide in HTML. After working with the abs-guide, read the Bash man page. There are quite a few things there that don't appear in the guide. Yes, I know it's long. 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? > 2. Issue "service network restart" with "strace" turned on. (I've never > used strace.) strace gives lots of output which generally isn't friendly to read. Invoking 'strace /etc/init.d/networking restart' gives me 325 lines of output, which isn't bad. If nothing else you might be able to run it when things work and when they don't and compare the output. Don't forget to redirect the stderr output to stdout with 2>&1. > Is there an easier and/or better approach? 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. Not sure what else to suggest at the moment. -- 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
