netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Bonding MAC address
@ 2016-10-28 11:09 Igor Ryzhov
  2016-10-28 16:39 ` Shanker Wang
  0 siblings, 1 reply; 2+ messages in thread
From: Igor Ryzhov @ 2016-10-28 11:09 UTC (permalink / raw)
  To: netdev

Hello everyone,

Studying the bonding driver I found that bonding device doesn't choose a new MAC address when the slave which MAC is in use is released.
This is a warning about that - "the permanent HWaddr of slave is still in use by bond - set the HWaddr of slave to a different address to avoid conflicts".
Why not to choose a new MAC for bonding device? Is it intentional or just not implemented?

Best regards,
Igor

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Bonding MAC address
  2016-10-28 11:09 Bonding MAC address Igor Ryzhov
@ 2016-10-28 16:39 ` Shanker Wang
  0 siblings, 0 replies; 2+ messages in thread
From: Shanker Wang @ 2016-10-28 16:39 UTC (permalink / raw)
  To: Igor Ryzhov; +Cc: netdev

[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]

I think it is intentional. Because changing mac address of an 
interface would cause problems. As a result, if you find it 
necessary to change the mac address, it should be done manually.

Consider these two example:

* A host is connecting the internet through a bond interface, 
and obtain ip address from a dhcp server. Changing the mac 
address automatically would possibly lead to re-assigning a 
new IP address, which could not be expected.

* A linux-box is acting as a gateway, providing service to 
hosts in the local lan. Changing mac address and not changing
IP address of an interface would cause other hosts to fail
to communicate with the gateway, since the old mac address is
still in theirs arp cache table. The communication will recover
after arp cache expires, which can be a short or long time.

* The scene is the same to the second one. And consider if  
arp snooping or other mechanisms to protect hosts from being 
spoofed by a fake gateway are enabled in the local lan. After 
changing the mac address, the linux-box itself will be a 
“spoofer” and may get blocked. 

So changing mac address of an interface could be dangerous and
lead to network malfunction and cannot be done automatically. 

> 在 2016年10月28日,19:09,Igor Ryzhov <iryzhov@nfware.com> 写道:
> 
> Hello everyone,
> 
> Studying the bonding driver I found that bonding device doesn't choose a new MAC address when the slave which MAC is in use is released.
> This is a warning about that - "the permanent HWaddr of slave is still in use by bond - set the HWaddr of slave to a different address to avoid conflicts".
> Why not to choose a new MAC for bonding device? Is it intentional or just not implemented?
> 
> Best regards,
> Igor


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3599 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-10-28 16:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-28 11:09 Bonding MAC address Igor Ryzhov
2016-10-28 16:39 ` Shanker Wang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).