Also, if you're getting strange slow-downs/poor performance: # mtr
(both a cli and gui) will show a continuously-probing traceroute result, often showing where congestion/failure is occurrring. (I use -n flag first to eliminate DNS lookups as a variable.) There's also some web tools such as speedtest.net and pingtest.net if things are mostly working to start tuning things like traffic shaping and MTUs. (That's another thing to check--is your ISP throttling you? You may have hit/exceeded a quota and are incurring their wrath of throttling down to 128kbps or less, depending on your provider...) Lastly, if you're getting bizarre behavior, you can go down to bare bones and use wireshark/tcpdump/airsnort/etc to capture packet streams and see what's going on. Hopefully a last resort, but has proven helpful in the past for example, wireshark will let you instantly see that you have multiple DHCP servers responding on the network conflicting with each other. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
