> i normally do this in modprobe.conf as something hinky happens on > dells with more than 2 ethernet ports and udev > :-) What lines do you add to modprobe to achieve this? Out of interest... > > > > > Can you point me to the documentation that supports removing hwaddr > > lines... It is also likely that the manipulation of configuration files > > differs from distro to distro... > > > > http://www.linuxquestions.org/linux/answers/Networking/Linux_bonding_how to > _0 > > also from bonding.txt > > All interfaces that are part of the trunk, should have SLAVE and MASTER > definitions. For example, in the case of RedHat, if you wish to make eth0 > and > eth1 (or other interfaces) a part of the bonding interface bond0, their > config > files (ifcfg-eth0, ifcfg-eth1, etc.) should look like this: > > DEVICE=eth0 > USERCTL=no > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > BOOTPROTO=none > > from bond_main.c > Hmmm, that does not specifically say remove the hwaddr line... > > The only reason i think this is that i have had problems with bonding > with RH5.1 where i had the HWADDR values specified. bond0 wouldn't > come up until i removed - indeed the box wouldn't boot - until i > removed those lines from ifcfg-eth0 and 1 > > I could be wrong, i often am Indeed, but so could I. I asked a question about consistent naming for ethernet device on rhel5 mailinglist and one recommendation was to keep the hardware address in the icfg-ethx files. Have a look at the thread in the arcives called "Persistent naming for eth devices" https://www.redhat.com/mailman/listinfo/rhelv5-list Regards > > best wishes > > mike > > > The bonding driver documentation states that you can specify options for > > the bond interface in the ifcfg-bondX file but that has not been the > > case for me. I still have to specify options in the /etc/modprobe.conf > > file. > > > > Regards > > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
