This has been filed as bug #1288196 with Ubuntu, but no fix from that side so far. IPv6 with SLAAC (Stateless Auto Configuration). This behavior makes the MAC address selection inconsistent between reboots and that might cause problems with: The first device to be plugged into the bonding device determines which MAC address the bonded device gets.ĭue to hardware timing it might be p9p1 OR p10p1 which is the first. When a slave fails, join or leaves the bond, the traffic is redistributed sending those updates again.With the ‘new’ style for configuring bonding under Ubuntu your bond device will not always have the same MAC address across reboots.įor example, you configure your bond in the /etc/network/interfaces file: auto p9p1ĭuring boot, both interface p9p1 and p10p1 will be hot-plugged under bond0. Notice that, in this mode, the receiving is also balanced and it is done by sending updates (ARP replies) to all remote peers with their individually assigned hardware address such that the traffic is redistributed. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave. The master interfaces uses the address of the current active slave (first enslaved). Works the same as in mode balance-rr/0Įach slave keeps its own MAC address. When aįailover happens and the interface changes to active, its MACĪddress is changed to be the master MAC address. MAC address, so all backup interfaces remains unchanged. The master interface MACĪddress changes during the failover to be the address of currentįollow or 2 - The master interface uses the first enslavement interface MACĪddress to start, but subsequent enslavements keeps the original The MACĪddress is configured at the enslavement.Īctive or 1 - Each slave keeps its own MAC address. None or 0 - default behavior, all slaves use the same MAC address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |