Cisco Cisco IPICS Dispatch Console Licensing Information

*  Changes :

*    - 2000/10/02 Willy Tarreau <willy at meta-x.org> :

*       - few fixes. Master's MAC address is now correctly taken from

*         the first device when not previously set ;

*       - detach support : call BOND_RELEASE to detach an enslaved interface.

*       - give a mini-howto from command-line help : # ifenslave -h

*

*    - 2001/02/16 Chad N. Tindel <ctindel at ieee dot org> :

*       - Master is now brought down before setting the MAC address.  In

*         the 2.4 kernel you can't change the MAC address while the device is

*         up because you get EBUSY.

*

*    - 2001/09/13 Takao Indoh <indou dot takao at jp dot fujitsu dot com>

*       - Added the ability to change the active interface on a mode 1 bond

*         at runtime.

*

*    - 2001/10/23 Chad N. Tindel <ctindel at ieee dot org> :

*       - No longer set the MAC address of the master.  The bond device will

*         take care of this itself

*       - Try the SIOC*** versions of the bonding ioctls before using the

*         old versions

*    - 2002/02/18 Erik Habbinga <erik_habbinga @ hp dot com> :

*       - ifr2.ifr_flags was not initialized in the hwaddr_notset case,

*         SIOCGIFFLAGS now called before hwaddr_notset test

*

*    - 2002/10/31 Tony Cureington <tony.cureington * hp_com> :

*       - If the master does not have a hardware address when the first slave

*         is enslaved, the master is assigned the hardware address of that

*         slave - there is a comment in bonding.c stating "ifenslave takes

*         care of this now." This corrects the problem of slaves having

*         different hardware addresses in active-backup mode when

*         multiple interfaces are specified on a single ifenslave command

*         (ifenslave bond0 eth0 eth1).

*

*    - 2003/03/18 - Tsippy Mendelson <tsippy.mendelson at intel dot com> and

*                   Shmulik Hen <shmulik.hen at intel dot com>

*       - Moved setting the slave's mac address and openning it, from

*         the application to the driver. This enables support of modes

*         that need to use the unique mac address of each slave.

*         The driver also takes care of closing the slave and restoring its

*         original mac address upon release.

*         In addition, block possibility of enslaving before the master is up.

*         This prevents putting the system in an undefined state.

*

*    - 2003/05/01 - Amir Noam <amir.noam at intel dot com>

*       - Added ABI version control to restore compatibility between

*         new/old ifenslave and new/old bonding.

*       - Prevent adding an adapter that is already a slave.