Transmit timed out error?

[Glenn]

The eepro100 driver has had a history of having problems with multicast
lists, which apparently netatalk uses. 

Donald Becker mentioned that he was working on some new multicast filter
code, hopefully for 1.06.  [BTW, thanks for a great driver, Donald]

A quick search of the linux-atalk@netspace.org mailing list found the
following, but I haven't tried it, as I haven't tried setting the
multicast_filter_limit to 0 (as I mentioned below), either.

Follow-ups to this discussion should probably be directed to the
linux-atalk mailing list.

Glenn Strauss
Brown University
<gs@lsd.brown.edu>

PS: Macs capable of AFP over TCP (a.k.a AppleShare IP like)
will default to using TCP/IP instead of the AppleTalk and
the AppleTalk DDP stack if you have netatalk+asun package.
Since afpd doesn't require atalkd to be started if you are
only using TCP/IP, not starting atalkd has worked for me.
(If you have afpd configured to use both DDP and TCP, then
you need to start atalkd)

FROM LINUX-ATALK@NETSPACE.ORG:
-----------------------------------------------------------
Date: Wed Dec 16 02:15:34 1998
Reply-To:     Appletalk on Linux <LINUX-ATALK@NETSPACE.ORG>
Sender:       Appletalk on Linux <LINUX-ATALK@NETSPACE.ORG>
From:         Joachim von Thadden <thadden@BBAW.DE>
Organization: Berlin-Brandenburgische Akademie der Wissenschaften
Subject:      Re: EEPro100b and Netatalk...
Content-Type: text/plain; charset=us-ascii

Oh, oh, there is a prolem with the eepro100-Driver which can bing your
system down. We had this problem and Alax Cox wrote, that it ca be
solved with the command

ifconfig eth0 allmulti

Since that day everything works realy fine with Netatalk!

Hans Johnson wrote:
>
> At 11:10 AM -0400 6/19/98, Dave DeMaagd wrote:
> >I have heard that there is problems with one of the Intel Ether Express
> >NICs and Netatalk (something with multicasting, I believe).
> >
> >Is the EEPro100b OK to use with Netatalk, because I would like to
upgrade
> >the networ to 100mbs, and have had generally good experiences with that
> >card in the past?
>
> Well, I've got an Intel EEPro100+, and it works great for Appletalk.. :)
>
> >Dave DeMaagd - demaagd@slashdot.org - www.cs.hope.edu/~demaagd
> >Guinness - You can't see a halogen desk lamp trough it!
> >SysAdmin/Programmer - TheImageGroup

--
MfG/Sincerely
                Joachim von Thadden

---------------------------------------


On Wed, 16 Dec 1998, Scott Stone wrote:

> On Tue, 15 Dec 1998, Glenn wrote:
> 
> > 
> > I've been running afpd WITHOUT atalkd with the additional line in my
> > conf.modules: options eepro100 multicast_filter_limit=3
> > on 2.0.36 with eepro driver 1.05 with good results -- or rather, 
> > without more than one ethernet driver hickup in the last month.  The
> > machine is lightly loaded, and is on a 100 MB switched ethernet segment.
> 
> hm, with the default eepro100 driver in the 2.0.36 kernel, I can make the
> TX shut down entirely inside 10 minutes with almost no load.  Maybe I
> should get that 1.05 driver..
> 
> > 
> > Someone had suggested setting the filter limit to 0 and running atalkd,
> > but I haven't tried that; I've been content with only running afpd over
> > TCP/IP (AFP over TCP), without the Appletalk DDP even compiled into the
> > kernel.  (Not running atalkd just means that server doesn't show up in
> > Chooser, but can still be accessed via server IP address)
> 
> I'm not running over TCP/IP, though - maybe that makes a difference here?
> 
> --------------------------------------------------
> Scott M. Stone <sstone@pht.com, sstone@pht.co.jp>
> Head of TurboLinux Development/Systems Administrator
> Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)
> 
> 
>