Re: [Nolug] Cox Connection Dropping

On Tue, 12 Oct 2004, Matthew Landry wrote:

> Thanks for the info. However, I'm not sure how I'd go about getting the
> server for the ps2 or xbox. Any ideas?

If have a linux firewall/router, you could run tcpdump to see where the
xbox/ps2 is connecting. But if the problem happens at random times to
random sites for random durations, it will be very hard to track down that
way.

I would start at the other side, and monitor the last mile between you
and Cox. Do a traceroute and get the ip of your nearest upstream Cox
router, ie the ip one hop from your own router. Try to ping it, hopefully
Cox isn't blocking icmp on their routers. Run the script below from cron
every few minutes to log when you lose connection to your upstream router.
I wrote this script to bounce the interfaces on my wireless linux box, as
the wireless is kinda flaky.

#!/bin/sh

/usr/local/sbin/fping -c1 192.168.1.1 > /dev/null

#connection is down...do some stuff
if [ $? != "0" ]
then
   echo "Wireless down. Restarting network." > /tmp/dsl.$$
   /sbin/service network restart > /dev/null
   echo "`date` Wireless restart" >> /var/log/dslchk
   echo "Restart done." >> /tmp/dsl.$$
   cat /tmp/dsl.$$ | mail -s'beavis network restart' ray@selu.edu
   rm -rf /tmp/dsl.$$
fi

Look around for fping, as it works a little better than ping. Use the Cox
router IP for the fping. If you get any false positives, try changing c1
to c3 or c5. I start with the first upstream router, as when i've had
similar problems before with both cable or dsl, most of the time the
problem happens in the last mile.

Once satisfied with your last mile connection, you could also change the
IP to yahoo or some other pingable address. Then when the connection is
down, that's when you want to do a few traceroute's to different sites
that you connect to. Log the time and output of the traceroutes and see
if you can make any corrolation about where the connection is being
dropped. (Make sure time is right and use traceroute -n since DNS prolly
ain't working if you're down...)

Having the traceroute output, and date/time should really help Charles
figure out where the problem is occuring.

ray

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ray DeJean  				       	 http://www.r-a-y.org
Systems Engineer                    Southeastern Louisiana University
IBM Certified Specialist  	      AIX Administration, AIX Support
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
___________________
Nolug mailing list
nolug@nolug.org