On Tue, Nov 22, 2005 at 07:19:19PM +0900, Sugihara Tomoe wrote: > > Hi, > > I have the same problem as Mr. Horman mentioned, using > latest /Documentation/networking/ifenslave.c. > I think the patch: > > http://galileo.gamepoint.com.au/pub/linux/kernel/people/akpm/patches/2.6/2.6.3-rc1/2.6.3-rc1-mm1/broken-out/linus.patch > > caused this problem. Could you spend a short time checking > your version of ifenslave when you have a chance. > And, does anyone have idea why the change , which cause the error > if a master interface has no IP addresses, was made? > That looks like the change. I can't say why it was made, save for whats in the changelog entry. Suffice it to say the fix is currently in -mm, so you should be able to fix the problem by getting that version
Regards Neil > Command output is as follows. > --------------------------------- > > $ ./ifenslave.new -v > ifenslave.c:v1.1.0 (December 1, 2003) > o Donald Becker ([EMAIL PROTECTED]). > o Detach support added on 2000/10/02 by Willy Tarreau (willy at meta-x.org). > o 2.4 kernel support added on 2001/02/16 by Chad N. Tindel > (ctindel at ieee dot org). > Usage: ifenslave [-f] <master-if> <slave-if> [<slave-if>...] > ifenslave -d <master-if> <slave-if> [<slave-if>...] > ifenslave -c <master-if> <slave-if> > ifenslave --help > > $ ./ifenslave.new bond1 eth1 > > Slave 'eth1': Error: set address failed > Master 'bond1', Slave 'eth1': Error: Enslave failed > > ----------------------------- > > > The former version works fine as follows insted of > a lot of warning messeges. > > ---------------------------- > $ ./ifenslave.old -v > > ifenslave.c:v1.0.12 (June 30, 2003) > Donald Becker ([EMAIL PROTECTED]). > detach support added on 2000/10/02 by Willy Tarreau (willy at meta-x.org). > 2.4 kernel support added on 2001/02/16 by Chad N. Tindel (ctindel at ieee dot > org. > DEBUG: argc=2, optind=2 and argv[optind] is (null). > The result of SIOCGIFFLAGS on lo is 49. > The result of SIOCGIFADDR is 00.00.7f.00. > The result of SIOCGIFHWADDR is type 772 00:00:00:00:00:00. > The result of SIOCGIFFLAGS on bond0 is 1443. > The result of SIOCGIFADDR is 00.00.ffffffac.10. > The result of SIOCGIFHWADDR is type 1 00:11:09:XX:XX:XX > The result of SIOCGIFFLAGS on bond0:0 is 1443. > The result of SIOCGIFADDR is 00.00.ffffffac.10. > The result of SIOCGIFHWADDR is type 1 00:11:09:XX:XX:XX > > > $ ./ifenslave.old bond1 eth0 > Something broke getting the master's IP address: Cannot assign requested > address. > Something broke getting the master's destination address: Cannot assign > requested address. > Something broke getting the master's broadcast address: Cannot assign > requested address. > Something broke getting the master's netmask: Cannot assign requested address. > Something broke setting the slave's address: Invalid argument. > Error setting the slave (eth0) with SIOCSIFDSTADDR: Invalid argument. > Something broke setting the slave (eth0) broadcast address: Invalid argument. > Something broke setting the slave (eth0) netmask: Invalid argument. > ------------------------------------ > > Of course works fine with Mr. Horman's patch, too :-) > I would appreciate any comment. > > Best Regards, > Tomoe Sugihara > > At Fri, 4 Nov 2005 23:08:32 -0800, > Jason R. Martin wrote: > > > > On 11/4/05, Neil Horman <[EMAIL PROTECTED]> wrote: > > > On Fri, Nov 04, 2005 at 12:25:49PM -0800, Jay Vosburgh wrote: > > > > > > > > [dropped linux-kernel; added netdev] > > > > > > > > Neil Horman <[EMAIL PROTECTED]> wrote: > > > > > > > > >The current version of ifenslave fails to attach slave interfaces to a > > > > >bond if > > > > >the masters doesn't have appropriate IP information. While its common > > > > >for > > > > >bonded interface to have IP information its not required (bond as part > > > > >of a > > > > >bridge for instance). > > > > > > > > As far as I know, attaching slaves to a bonding device without > > > > an IP address works just fine; the bonding master device must merely be > > > > up. Under what circumstances are you seeing a problem? > > > > > > > Try to run ifenslave on a bonded interface with no ip address, it will > > > fail. > > > > Are you sure it fails or do you just get an error message? > > Traditionally it has spit out a (non-fatal) error message about not > > being able to get the address info, but then go ahead and enslave > > anyway. > > > > At least that's been my experience. > > > > Jason > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: > > Tame your development challenges with Apache's Geronimo App Server. Download > > it for free - -and be entered to win a 42" plasma tv or your very own > > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > > _______________________________________________ > > Bonding-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/bonding-devel > > -- /*************************************************** *Neil Horman *Software Engineer *gpg keyid: 1024D / 0x92A74FA1 - http://pgp.mit.edu ***************************************************/ - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
