Looking on the linux bonding driver, it seems to unconditionally (*)
assume that the enslaved device supports the set_mac_address call.
>From reading the doc (Documentation/networking/bonding.txt) i understand that
it is **not** a must prerequisite for the active-backup mode, this is since
there is at most one active slave at each point of time and as the doc states:
when a failover occurs in active-backup mode, bonding will issue
one or more gratuitous ARPs on the newly active slave.
I'd like to get feedback from people here if you think it makes sense
to change the bonding driver to actually allow for active-backup/bonding
with network device drivers which does not support set_mac_address.
thanks,
Or Gerlitz.
(*) in the sense that it checks for each enslaved device and reports
an error if dev->set_mac_address is not supported and later use
dev_set_mac_address elsewhere in the code.
-
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
