[conspire] running ifconfig - getting errors and collisions

[Daniel Gimpelevich]

On Tue, 30 May 2006 17:46:35 -0700, Darlene Wallach wrote:

> A. P. Godshall wrote:
>> On 5/30/06, Ryan Russell <ryan at thievco.com> wrote:
>> 
>>> 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
>>>
>>> Once the name is resolved, connectivity looks good.  At least, for these
>>> 8 packets in that 3 second window.
>> 
>> ...
>> 
>> I had some serious DNS problems with SBC (none with speakeasy) and had
>> a better time after I ran dns through pndsd (apt-get install pdnsd).
>> 
>> Are you sure it's a connectivity issue rather than a DNS issue?
>> 
>> 
> 
> Good point! I'm not sure it's a connectivity issue. I assumed
> it was a connectivity issue.
> 
> The line carrier is SBC. At least that is what DSL Extreme reported
> when I tested availability.
> 
> What steps do I take to determine if it is connectivity vs DNS
> vs something else?
> 
> Thank you,
> 
> Darlene

This is the reason that I suggested trying to ping a known numeric IP
address. Doing so takes DNS service out of the equation entirely for the
purpose of the test.