From: jamal <hadi@cyberus.ca>
To: David Shwatrz <dshwatrz@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
yoshfuji@linux-ipv6.org, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-2.6][NEIGH] Updating affected neighbours when about MAC address change
Date: Mon, 24 Dec 2007 09:50:59 -0500 [thread overview]
Message-ID: <1198507860.9642.53.camel@localhost> (raw)
In-Reply-To: <31436f4a0712240538n1b65c2a8u35109ce4c69a00d5@mail.gmail.com>
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.
next prev parent reply other threads:[~2007-12-24 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-23 11:41 [PATCH net-2.6][NEIGH] Updating affected neighbours when about MAC address change David Shwatrz
2007-12-23 12:11 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 12:24 ` David Shwatrz
2007-12-23 12:38 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 12:46 ` jamal
2007-12-23 13:04 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 13:17 ` jamal
2007-12-24 14:33 ` jamal
2007-12-23 13:04 ` David Shwatrz
2007-12-23 13:13 ` YOSHIFUJI Hideaki / 吉藤英明
2007-12-23 13:21 ` David Shwatrz
2007-12-23 14:02 ` Herbert Xu
2007-12-24 13:38 ` David Shwatrz
2007-12-24 14:50 ` jamal [this message]
2007-12-25 0:53 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1198507860.9642.53.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=dshwatrz@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).