Deja Vu all over again

[John F. Kohler]

ME wrote:

> On Sun, 1 Apr 2001, John F. Kohler wrote:
> > 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
>
> What happens when you try to perform pings to the linux box's IP address
> from one of the macs using that utility you mentioned? Do they say they
> are successful?

Not all. I just ran the utility "Mac TCP Watcher" during dinner. it sent
1580 pings, and 1183 (74%) were returned.  397 (25%) were lost.
Minimum transit time was .01 seconds, average .08 seconds
and maximum was .11 seconds.  I watched the pings
go out in groups of 10 before the window would refresh
and 3 or 4 packets out of 10 (on average) would record
"echo timed out."  Strange, because it was only going 50 feet to the
router, and 50 feet back to the machine on the same desk.

>
>
> If they claim no success while the linux box claims partial success, then
> there is likely a problem with how this card is being recognized by your
> linux kernel. It is possibl that support for your card is not mature, or
> there might be sume bugginess in the hardware to complicae things.

Next I set the Linux box to ping the Mac LC.  51 packets transmitted 40 packets received.
21% packet loss
round-trip min/avg/max/mdev  =1.609/1.762/4.853/0.51 ms

>
>
> If the mac reports the same problem, it may also be a hardware problem or
> a software problem.
>
> You might be able to download the diskette from the "old" ethenret card
> manufacturer's web site and check the IRQs used by it.
>

I have asked my son in Cotati to download a good copy of the Vendor setup
disk and send it to me.



>
> As another option, you can look into making your old ethernet card work
> with an installation of RedHat and then add the "new" card and have 2
> ethernet cards in your box. From there, you can at least test one and
> diconnect the other one during testing.
>

Would one be identified as eth1 and the other eth0?

>
> If you have a Windows box lying around, or have windows installed
> somewhere, you can try using the same card with windows. If you have the
> same problems, it is likely to be a hardware issue. If there are no
> problems with windws, then that would point to a problem with the way
> linux is trying to talk with your NIC.

I have no Windows box. I don't even like to think the word "Microsoft."

>

John

>
>
> -ME