Deja Vu all over again

[John F. Kohler]

ME wrote:

> On Sun, 1 Apr 2001, John F. Kohler wrote:
> > The new (Jameco) card is back in place, and re-seating it may have been
> > fortunate.  I have 4 terminal windows up on the GNOME desktop, all pinging the respective
> > router ports.
> > 192.168.1.1 (router)
> > 192.168.1.2 (Mac LC)
> > 192.168.1.3( iMac)
> > 192.168.1.4 (Linux box)
> > typical range of ping response for the router is 700-800 usec
> > typical range of ping response for the LC is 1.6 to 1.7 msec
> > typical range of ping response for the iMac is 700-800 usec
> > typical range of ping respons for the linus is 48-70 usec
>
> Well, then let's assume that they are reachable. Next, try to ping
> something outside your network:

I did, in fact, ping the S. F. Chronicle web page www.sfgate.com (209.1.99.80) before leaving
the house this morning:  It was doing "Destination Host Unreachable"
when I came home with the following statistics:
23995 packets transmitted, 4246 packets received  +2 duplicates (?)
+12350 errors, 82% packet loss

During the same time I was pinging the router (192.168.1.1) for about the same duration:

27037 packets transmitted, 6269 packets received + 6215 errors 76% packet loss

During the same time I had the linux box pinging its own address in the router:

27493 packets transmitted 27493 packets received, 0% loss
round-trip min/avg/max/mdv = 0.032/0.063/2.893/0.040 ms

>
>
> # ping -c 50 130.157.2.5

"Destination host unreachable"
Rebooted linux, and got the same
"Destination......"
Tried to ping the router: (192.168.1.1)
Same... "Destination....."

>
> Let it run for a bit, if that returns positive results then let's
> continue...
>

Sorry. No luck yet.  I am re-booting linux but not to hopeful.
Next time I'll boot from a power off mode. This problem seems intermittent
after some running.
John

>
> # nslookup www.whitehouse.gov
>
> Does the nslookup return something like:
>
> Server:  ns1?.earthlink.net
> Address:  IP.Address.for.an-earthlinkserver
>
> Name:    www.whitehouse.gov
> Addresses:  198.137.240.91, 198.137.240.92
>
> Is the above reported?
>
> If so, then let us continue...
>
> Since you say you have GNOME up an running, try launching netscape. See if
> you are able to browse the web. If not, then we can try other things.
>
> > I do, in fact have a mac utility on my LC desktop "Mac TCP watcher, "
> > which allows me to do several tasks including to ping the rest of the network,
> > as well as URLs in the outside world.  I have seen the "traceroute" feature,
> > but seldom used it.  I don't know the purpose of it.
>
> Go ahead and use this to ping your linux box. I suspect it will work, but
> it would be good to verify it anyway.
>
> "traceroute" is a tool to tell you how many router hops exist between you
> and another point on the internet - assuming all your packets take that
> route. (There is no guarantee that all of your traffic will necessarily
> follow that path all of the tme, but it is likely it will travel that
> route most of the time.)
>
> Here is an example of traceroute:
> dugan at nerds:~$ /usr/sbin/traceroute bolt.sonic.net
> traceroute to bolt.sonic.net (208.201.224.36), 30 hops max, 38 byte
> packets
>  1  nerds2.passwall.com (10.0.0.1)  1.436 ms  0.862 ms  0.823 ms
>  2  adsl-209-204-181-1.sonic.net (209.204.181.1)  20.538 ms  24.879 ms
> 16.212 ms
>  3  bolt.sonic.net (208.201.224.36)  18.108 ms  16.810 ms  16.041 ms
>
> In the above, my machine's packets must pass through my router
> "nerds2.passwall.com" and the number that follow are a measure of
> latency. By doing three tests it helps you to get an average. Then my
> router hands off the packet to another router
> "adsl-209-204-181-1.sonic.net who then gets the packet to where it needs
> to go at bolt.sonic.net.
>
> The above is a fairly short traceroute path. When I perform one to an SSU
> server, I pass about 15 hops as routers diirect the packets on their way,
> getting closer to the destination.
>
> traceroute can be useful to find out if a link between you and anoter
> location is down, or troubeshoot "loops" in routing policies.
>
> Check out the manpage for traceroute on your linux box for a more detailed
> review.
>
> -ME