Bonding on 2.4.3, ifenslave wierdness
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Aaron Van Couwenberghe avancouw at calpoly.eduSat Apr 21 17:58:49 PDT 2001
- Previous message: channel bonding
- Next message: Bonding on 2.4.3, ifenslave wierdness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greetings - At work we've been using Willy Tarreau's channel bonding patches against linux 2.2.17, and it's been working just fine for us. Now, though, we need to upgrade our systems to kernel 2.4.x (specifically 2.4.3), and we've been having bad luck with the included driver. I'm using the ifenslave.c available from beowulf.org that went with bonding.c 0.2 (ifenslave.c 0.7, Don Becker's version). I'm not sure if there is a new one for the 2.4 kernel's driver.... I follow the directions precisely, but it appears that rather than inheriting its MAC address from the first slave interface, bond0 tries to push *its* MAC into every enslaved device. So I get HWaddr 00:00:00:00:00:00 across the board. It's also trying to set wrong IP/netmask/broadcast settings. Here are the commands I've executed: (after starting without networking...) ifconfig bond0 10.0.0.3 netmask 255.255.255.0 broadcast 10.0.0.255 up ifenslave -v bond0 eth0 here is the resulting output: ifenslave.c:v0.07 9/9/97 Donald Becker (becker at cesdis.gsfc.nasa.gov) The hardware address (SIOCGIFHWADDR) of bond0 is type 1 00:00:00:00:00:00. The interface eth0 is up, shutting it down it to enslave it. Set the slave's hardware address to 00:00:00:00:00:00. Set the slave's IP address to 0.0.10.0. Set the slave's MTU to 1500. Set the slave's destination address to 0.0.10.0. Set the slave's broadcast address to 0.0.10.0. Set the slave's netmask to 0.0.255.255. Set the slave's flags 1043. DEBUG: argc=4, optind=2 and argv[optind] is bond0. SIOCSIFSLAVE: Invalid argument. Now, I really don't know what's going on here; it seems almost as if ifenslave is making these values up. What should I do? Do I have the wrong version of ifenslave? I wind up with eth0 configured but at hwaddr 0 just like bond0. Note that I'm running these commands before *anything* touches any network devices. Thanks in advance for any help. -- ..Aaron Van Couwenberghe... ..avancouw at calpoly.edu.. ..aaronv at debian.org.. Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org A witty saying proves nothing. -- Voltaire
- Previous message: channel bonding
- Next message: Bonding on 2.4.3, ifenslave wierdness
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
