TIPC handling of ethernet mac address change

2 messages, 2 authors, 2012-08-23 · open the first message on its own page

TIPC handling of ethernet mac address change

From: Chris Friesen <hidden>
Date: 2012-08-22 15:36:45

Hi,

I'm pretty new to tipc so pardon me if I use the wrong terminology. :)

I'm using TIPC 1.7.7 and bonding.  I'm seeing some strange behaviour 
when the bond MAC address changes--the tipc LINK_CONFIG messages still 
contain the old MAC address embedded in them.  This causes the other end 
to send back to us on the wrong MAC and the packets get dropped.

I see recv_notification() has a case for NETDEV_CHANGEADDR so it looks 
like MAC address change was intended to be handled, but I'm not entirely 
clear on where the MAC address is supposed to be changed.

Any assistance on debugging/patching this would be appreciated.

Chris


-- 

Chris Friesen
Software Designer

3500 Carling Avenue
Ottawa, Ontario K2H 8E9
www.genband.com

Re: TIPC handling of ethernet mac address change

From: Ying Xue <hidden>
Date: 2012-08-23 06:56:35

Hi Chris,

You are right.

Currently TIPC does not handle the change of mac address.
So I will submit a related patch to fix the issue to net-next tree.

Thanks for your report.

Regards,
Ying


Chris Friesen wrote:
Hi,

I'm pretty new to tipc so pardon me if I use the wrong terminology. :)

I'm using TIPC 1.7.7 and bonding.  I'm seeing some strange behaviour 
when the bond MAC address changes--the tipc LINK_CONFIG messages still 
contain the old MAC address embedded in them.  This causes the other 
end to send back to us on the wrong MAC and the packets get dropped.

I see recv_notification() has a case for NETDEV_CHANGEADDR so it looks 
like MAC address change was intended to be handled, but I'm not 
entirely clear on where the MAC address is supposed to be changed.

Any assistance on debugging/patching this would be appreciated.

Chris
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help