[H-GEN] Re: intermittent cable connxn outage

Wed Dec 8 01:19:24 EST 2004

* Scott Burns <sburns at ihug.com.au> :
> Troy Piggins wrote:
> >Hi.  I posted this today on comp.unix.admin, but need help real
> >quick.  This internet not working is crippling business (aint it
> >always )
> >
> >I am totally stumped by this, and seek some advice on either a
> >solution or possible course of action to locate the problem.
> >
> >The problem is that just yesterday and today the connection to
> >internet is only working intermittently.  By this I mean that it works
> >for hour or so, then can't see anything outside (ping, DNS etc), then 
> >it works for a while, then not.
> >
> >
> 
> A few questions:
> 
> 1) How do you connect to the internet?  Cable modem?  What type?  Make 
> and model?  USB or Ethernet?

Cable modem, motorola SB5100, connected via a second NIC on the
gateway.

> 2) What does your network look like?  Internet->Modem->RH9->LAN?

Correct

> 3) Can you provide a traceroute listing that shows the path out of your 
> network?

This is when the internet connxn is working:

 1  10.203.80.1 (10.203.80.1)  6.340 ms *  5.644 ms
 2  border-router (61.9.209.3)  6.451 ms  6.712 ms  7.961 ms
 3  GigabitEthernet4-2.cha23.telstra.net (139.130.193.117)  5.872 ms
6.465 ms
5.871 ms
 4  GigabitEthernet5-0.cha-core4.Brisbane.telstra.net (203.50.44.9)
6.195 ms  5
.999 ms  6.432 ms
 5  GigabitEthernet2-1.woo-core1.Brisbane.telstra.net (203.50.6.218)
8.559 ms
6.326 ms  7.564 ms
 6  Pos5-0.ken-core4.Sydney.telstra.net (203.50.6.221)  19.186 ms
19.176 ms  19
.978 ms
 7  10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86)
46.286 ms
19.316 ms  20.132 ms
 8  * i-0-2.syd-core01.net.reach.com (134.159.125.73)  20.548 ms
19.227 ms
 9  * i-7-0.syd-core02.net.reach.com (202.84.221.90)  20.669 ms
26.884 ms
10  i-5-0.tmhstcbr01.net.reach.com (202.84.144.201)  160.751 ms *
161.514 ms
11  i-1-2.iadv02.net.reach.com (202.84.144.154)  163.164 ms  174.555
ms  160.932
 ms
12  * i-1-1.iadv02.net.reach.com (207.176.96.61)  160.801 ms
161.633 ms
13  134.159.126.178 (134.159.126.178)  162.958 ms * *
14  210.184.124.3 (210.184.124.3)  176.005 ms  164.119 ms  162.789
ms
15  203.194.223.14 (203.194.223.14)  164.205 ms  176.227 ms  166.246
ms
16  64.233.175.13 (64.233.175.13)  163.548 ms  173.257 ms  164.469
ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *

When it is not working, nothing - unknown host telstra.com etc.

> 4) Anything of interest on the console (Ctrl-Alt-F1)?  In 
> /var/log/messages?  In fact, please skim /var/log/messages for sensitive 
> information then post this file somewhere we can look at it.  Rough 
> times of outages can help here.

I will ftp it to :

http://lowstump.com.au/var-messages.txt

When I can get connection again.

> 5) What is the output of ifconfig?  Any errors logged there?  Is the TX 
> and RX byte counts doing anything during outages?

eth0      Link encap:Ethernet  HWaddr 00:04:E2:40:E4:F0
          inet addr:147.10.92.105  Bcast:255.255.255.255
Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:104465 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9554 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:18218047 (17.3 Mb)  TX bytes:1018420 (994.5 Kb)
          Interrupt:11 Base address:0x8000

eth1      Link encap:Ethernet  HWaddr 00:0E:A6:1A:7B:EA
          inet addr:192.168.0.1  Bcast:192.168.0.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25302 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39639 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2168588 (2.0 Mb)  TX bytes:9078736 (8.6 Mb)
          Interrupt:11 Base address:0xec00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:9486 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9486 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9550310 (9.1 Mb)  TX bytes:9550310 (9.1 Mb)

Define TX/RX counts "doing anything"?  What are they?  Should they
be increasing in size?

> That should get us started.
> 
> Scott

Thanks mate - refer to my other email for some more information.

-- 
T R O Y  P I G G I N S
e : troy at piggo.com