Subject: Re: AppleTalk & EEpro100 cards (was Re: [netatalk-admins] Massive dropped connections - any ideas?)
From: a sun (asun@saul5.u.washington.edu)
Date: Mon Apr 26 1999 - 15:29:31 EDT
>Apr 20 18:34:34 MACHINE kernel: protocol 9b80 is buggy, dev eth0
>Apr 20 18:35:20 MACHINE kernel: protocol 0008 is buggy, dev eth0
>Apr 20 18:38:21 MACHINE kernel: protocol 0400 is buggy, dev eth0
>Apr 20 18:40:14 MACHINE kernel: protocol 3781 is buggy, dev eth0
>
>in /var/log/debug if you tcpdump eth0.
are you sure that this is from a linux 2.2.6 kernel? this is a
cosmetic bug that i fixed in 2.2.6. it only manifests when you stick a
network interface tap of some kind (e.g., tcpdump) on with appletalk
active.
>Apr 15 17:52:36 MACHINE kernel: eth3: Transmit timed out: status 0050
>0000 at 17015/17030 command 00000000.
>Apr 15 17:52:36 MACHINE kernel: eth3: Trying to restart the transmitter...
by definition, this has to be an ethernet card/driver problem.
>In order to isolate software from hardware, I tried the much older
>Univeral Appletalk Router (UAR 1.0.16 September 1995) which
>doesn't use the appletalk support in the linux kernel. This works
>absolutely fine. This leads me to believe (perhaps incorrectly)
>that the hardware and eepro100 driver are fine, but that either
>netatalk and/or kernel appletalk support is broken.
that's not necessarily true. the eepro100 card has some timing issues
w.r.t. multicast that atalkd has a tendency to aggravate. uar may not
be triggering things in the same way. usually, this turns out not to
be a problem because most people aren't using a many-zoned
network. before ruling out a driver/card problem, i would suggest
trying out a dec tulip card first.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:38 EST