Very Computer

    ARP:Bad packet received on device "eth0"!

continuously, at a rate of about once every 5 seconds. The ethernet link seems
to otherwise work OK. I can ftp and telnet from my machine and telnet into my
machine (at least to the point of getting the login screen).  If I fire up X,
the bash window does not display the error messages and ftp and telnet work
OK.  If I pull the ethernet cable from the jack, the messages stop.

I have read the NET-2 FAQ and, to the best of my knowledge, have followed
their recommendations to setup the basic TCP/IP services only.

My network card is a 3Com 3c503/16, using thin wire. My computer is a PC_Brand
486-25(DX) with 16M RAM and 8M+ swap partition.  The video adapter is an
Orchid ProDesigner II (TSENG 4000).

Any help would be appreciated.

================================================================

 Opinions expressed herein are exclusively my opinions and
 in no way represent NASA nor the U.S. Government. Anybody
 who thinks otherwise is just itching for a fight!
================================================================

I had the same problem some time ago. The solution was to install the
real pl11-kernel. Before I had a pl11-beta from SLS distribution.
Since I upgraded to pl11 everything works. You should check your
pl11.tar.gz against a version on sunsite, tsx-11 or other.

Tom.
--

--------------------------------------------------------------------------
Thomas Voss                                        Phone: +49 0241/807893
Institute of Semiconductor Electronics - II        Fax:   +49 0241/86165
Technical University Aachen
Germany

   I had the same problem some time ago. The solution was to install the
   real pl11-kernel. Before I had a pl11-beta from SLS distribution.
   Since I upgraded to pl11 everything works. You should check your
   pl11.tar.gz against a version on sunsite, tsx-11 or other.

   Tom.
   --

as I was and on the same local network. It turns out that one of the machines
on the net was sending ARP packets with a type = IEEE 802.2, which is different
than the type defined by my ethernet device which is type = 10MB Ethernet. The
IEEE 802.2 packets/headers were not addressed to either my machine or the original
poster, but the linux networking kernel portion considered it a bad packet
any...On a large local net such as ours (larc.nasa.gov) not being able to
handle packets of types other than that of the ethernet device can be a
problem. Add this to not being able to handle packet fragmentation makes linux
a major problem to use on a large network....

Anyone know how the net development effort is going? any idea when these problems
are going to be resolved ?

John

--
John Burton                      G & A Technical Software, Inc.