[conspire] running ifconfig - getting errors and collisions

[Darlene Wallach]

Daniel Gimpelevich wrote:
> First thing to look at would be the lights on the DSL modem. If there's
> nothing unusual there, try to ping a known numeric IP address. The third
> test is to ping a named host, like below. Since you're on DHCP, one thing
> you can try when you have a problem is to bring down eth0 and then bring
> it up again.
> 
> On Mon, 29 May 2006 17:04:58 -0700, Darlene Wallach wrote:
> 
> 
>>I recently got dsl. Connectivity seems to have been working
>>very well until today.
>>
>>I seem to keep losing connectivity and/or having connectivity
>>problems. Sometimes
>>$ ping -c4 www.google.com
>>ping: unknown host www.google.com
>>
>>$ ping -c4 www.google.com
>>PING www.l.google.com (66.102.7.99) 56(84) bytes of data.
>>64 bytes from 66.102.7.99: icmp_seq=0 ttl=246 time=10.9 ms
>>64 bytes from 66.102.7.99: icmp_seq=1 ttl=246 time=10.7 ms
>>64 bytes from 66.102.7.99: icmp_seq=2 ttl=246 time=10.4 ms
>>64 bytes from 66.102.7.99: icmp_seq=3 ttl=246 time=10.6 ms
>>
>>--- www.l.google.com ping statistics ---
>>4 packets transmitted, 4 received, 0% packet loss, time 3004ms
>>rtt min/avg/max/mdev = 10.446/10.689/10.929/0.186 ms, pipe 2
>>
>>$ /sbin/ifconfig
>>eth0      Link encap:Ethernet  HWaddr 00:D0:B7:79:FF:A2
>>           inet addr:68.183.66.92  Bcast:68.183.66.255  Mask:255.255.255.0
>>           inet6 addr: fe80::2d0:b7ff:fe79:ffa2/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:151416 errors:258 dropped:0 overruns:0 frame:258
>>           TX packets:111640 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:139 txqueuelen:1000
>>           RX bytes:168631221 (160.8 MiB)  TX bytes:11995948 (11.4 MiB)
>>
>>I called technical support - no reported problems.
>>
>>What could be causing the errors in RX and the collisions? Is there
>>something I can do?
>>
>>Are there other commands I can run to troubleshoot?
>>
>>Thank you,
>>
>>Darlene

Daniel,

Thank you.

I didn't think of trying a known numeric IP address.

The lights on the modem seem to be okay.  I had tried bringing
down eth0 and bringing it up again. When it wouldn't connect,
I powered off the hub and modem, counted to 15, powered them
back on and tried connecting again. It failed to connect for
a while, then I was able to connect. Not much time passed and
I lost connectivity again - that is when I called support. I
got connectivity again but don't know why I'm getting the
errors and collisions.

Darlene