On Mon, 2007-24-12 at 15:38 +0200, David Shwatrz wrote: > Hello, > > First, it indeed can be handled by user space. (even though it should > be done twice, once for ifconig of net-tools and once for ip of > iproute2)
it needs to be done once only: reacting to netlink events when MAC address changes. > / However, we have already > methods which deal with bringing down an interface - neigh_ifdown(), > and changing MAC address of an interface (neigh_changeaddr). So why > not do it from the kernel ? Herbert, i agree with you that userspace is the best spot for this[1]; we unfortunately have precedence already on the kernel sending arps with bonding when link status changes (that was added recently). So it sounds reasonable to have this patch in the kernel as well. cheers, jamal [1] Things like these tend to be very policy rich and thats why user space is the best spot for them. I have infact implemented this feature in user space in some random box i have where i failover MACs for HA reasons. Depending on how much traffic there is on the wire, arps do get dropped. One of the hardest things to decide on was how many times to retry the grat arp sending and what the timeout would be between each sent gratarp. The earlier patch posted didnt consider this but would be nice to have a couple of sysctls to add the two parameters if this makes it in. -- 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
