As you can see from the subject, I am trying to combine these two items =
and make them work together. So far, without much success.
Bonding works well for me normally, but when I try to launch atalkd (a =
part of the netatalk package), which should work with the bond1 =
interface, it fails. I am using mode=3D0 (round-robin LB) as my default. =
I have tried using other modes, mode=3D6 seems better somehow, but other =
components in my system don't work well with it. Using mode=3D1 =
(active-backup) proves to work the best, no problems seen at all.
I added lots of debug output to the appletalk module and the appletalk =
kernel sources, and found out that the expected behavior is for it to =
send aarp probes, with an appletalk address it tries to claim. When no =
one answers, it then claims this address and uses it. When using =
mode=3D0, the sending machine receives its own aarp probes, and it then =
decides that it cannot use this address, and goes on to the next =
I think that this is a bonding issue rather than an appletalk issue, =
since things seem to be working well without bonding, and also with some =
of the bonding modes. It's possible that I somehow exposed an appletalk =
bug, but the flow should be the same as far as the appletalk is =
concerned. It does indeed use the net_device struct, like many others, =
but does not do anything special with it.=20
Does anyone has a clue on how to proceed with this ?
From: Tim Mattox <tmattox@gm...> - 2004-10-03 19:12:08
I think you have your network miswired/misconfigured for
bonding mode 0. See below.
On Sun, 3 Oct 2004 18:47:37 +0200, Shlomi Yaakobovich <shlomi@...> wrote:
> When using mode=0, the sending machine receives its own
> aarp probes, and it then decides that it cannot use this address,
> and goes on to the next address, etc.
For bonding mode 0 in regular ethernet networking, you need
to either have the two (or more) NICs connected to separate
and isolated networks such that broadcast packets sent on
one NIC can't reach the other NIC on the same machine...
or your multiple NICs need to be connected to a switch that
understands and is configured for Linux Channel Bonding
(sometimes this is called "trunking"). The latter method may
not be sufficient for your needs.
What you just described is the aarp packets from a node
coming back to the node through one of it's other NICs in
the bond. That is the problem. Suppose you have two
NICs per machine in your setup, NIC A and NIC B. You
would need to connect all NIC A's to a switch A, and then
all NIC B's to a switch B.
And then make sure that switch A and switch B do NOT have
a connection to each other that would propagate broadcast
packets. The easy way is to not have switch A and switch B
have any connection to each other at all, except through
the bonded machines in question.
Tim Mattox - tmattox@... - http://homepage.mac.com/tmattox/