mcast troubles on bond interface ...

Hi all,

my trouble is getting a multicast address bound to the correct
interface on 1 particular machine. There are 11 other machines with
exact same hardware, where I don't have this problem. The only
difference I can spot is that on this 1 particular machine the listing
order of the devices is different from the working ones.

- working mcast machine "ipmaddr show ipv4" -
1: lo
inet 224.0.0.1
2: eth0
inet 224.0.0.1
5: eth2
inet 224.0.0.1
6: eth3
inet 224.0.0.1
7: eth4
inet 224.0.0.1
8: eth5
inet 224.0.0.1
11: bond0
inet 224.2.4.0
inet 230.1.2.3
inet 224.0.0.1
12: bond1
inet 224.0.0.1

This is how it's displayed on all the working machines, so first the
"lo", followed by the "ethN" devices and lastly the "bondN" devices...


- not working machine "ipmaddr show ipv4" -
1: lo
inet 224.0.0.1
2: eth0
inet 224.0.0.1
4: bond0
inet 224.0.0.1
5: bond1
inet 224.0.0.1
6: eth2
inet 224.0.0.1
7: eth3
inet 224.0.0.1
8: eth4
inet 224.0.0.1
9: eth5
inet 224.2.4.0
inet 230.1.2.3
inet 224.0.0.1

Notice the change in order of the listing, a plain "ip li" shows the
same order as "ipmaddr" ("ip maddr show" also) as oposed to
"ifconfig", which doesn't show this change in order...

This must somehow be related to the problems I'm having binding
multicast address to the bond0 in stead of the underlying slave eth5
(eth5 and eth3 are slaves of bond0, so it's not just randomly picking
an interface at least I guess)

I've read the NET-howto, but there's still no update on the mcast
section :-/ And in the "iproute" docs there's no mention about how
the listing-order of interfaces is derived ...

any idea anyone ?

bye,
gert


Gert