Subject: Re: [netatalk-admins] AppleTalk crashes EEPro100 on a bonded etherchannel
From: a sun (asun@saul3.u.washington.edu)
Date: Wed Nov 25 1998 - 14:35:53 EST
Sorry for my ignorance, but does this somehow mean that atalkd wont bond
to eth1, ignoring eth0 even if atalkd.conf only has a eth1 argument?
Reason I ask is this is how I have been trying to set netatalk up. I had
it working this way under 1.3, and for a little while under 1.4b2, but it
was unsatisfactory due to my ignorance, I've been at it again, and thus
far have been unable to get it to run at all.
umm, everything pre-asun2.1.1-3 will attempt to use any ethernet
interface. if you have more than one, you'll need to specify things
explicitly as atalkd needs to be set up to route between the various
interfaces in those cases. if you don't want routing to be done, you
can just specify one interface.
the little snippet i suggested just makes it so that atalkd will skip
slave interfaces. if you're doing ethernet bonding, you shouldn't be
running things on the slave interface anyway.
-a
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:33:46 EST