From: Tommi Virtanen <tv@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Change MAC without bringing interface down
Date: Mon, 18 Aug 2003 17:24:55 +0300 [thread overview]
Message-ID: <20030818142455.GA1793@lapdog> (raw)
In-Reply-To: <20030818041911.358c3437.davem@redhat.com>
On Mon, Aug 18, 2003 at 04:19:11AM -0700, David S. Miller wrote:
> On Mon, 18 Aug 2003 12:13:12 +0300
> > 1. makes eth_header_cache_update also update the source MAC in
> > hh_cache.
> >
> > 2. adds a NETDEV_CHANGEADDR notifier in net/core/neighbour.c
> > that walks through all the neighbour entries and updates
> > the hh_cache's for all the neighbour entries related to
> > given device.
> I would suggest to fix this by instead flushing the hh
> entries (just like neigh_destroy() does).
This may be a dumb question, but how do I do that?
If I set them to neigh_blackhole, like neigh_destroy() does,
e.g. already running gets -ENETDOWN. That's now true and it's
not nice. I'm having trouble seeing how to "disable" the
neighbour entry, so it won't be used again.
If I use neigh_suspect() in an attempt to mark the entry as
"expired", I see traffic using the "old" MAC as source after a
while. Apparently, it gets confirmed and then the old MAC
is used again.
> This way, we don't have to fix up every single header cache
> implementation, that's painful :(
I agree with that, though I am only interested in ethernet ;)
--
:(){ :|:&};:
next prev parent reply other threads:[~2003-08-18 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 9:13 [PATCH] Change MAC without bringing interface down Tommi Virtanen
2003-08-18 11:19 ` David S. Miller
2003-08-18 12:13 ` jamal
2003-08-18 12:12 ` David S. Miller
2003-08-18 13:03 ` jamal
2003-08-18 16:04 ` Tommi Virtanen
2003-08-18 16:06 ` David S. Miller
2003-08-18 17:11 ` Tommi Virtanen
2003-08-18 18:51 ` Arnaldo Carvalho de Melo
2003-08-19 5:50 ` Tommi Virtanen
2003-08-19 15:42 ` Arnaldo Carvalho de Melo
2003-08-19 19:31 ` David S. Miller
2003-08-18 14:24 ` Tommi Virtanen [this message]
2003-08-18 14:20 ` David S. Miller
2003-08-18 15:10 ` jamal
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=20030818142455.GA1793@lapdog \
--to=tv@debian.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).