From: Thomas Graf <tgraf@suug.ch>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: Patrick McHardy <kaber@trash.net>,
Brian Pomerantz <bapper@piratehaven.org>,
netdev@vger.kernel.org, davem@davemloft.net, pekkas@netcore.fi,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@coreworks.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [IPV4] Fix secondary IP addresses after promotion
Date: Sat, 5 Nov 2005 20:06:36 +0100 [thread overview]
Message-ID: <20051105190636.GU23537@postel.suug.ch> (raw)
In-Reply-To: <20051105183910.GA17215@ms2.inr.ac.ru>
> > Local routes for 10.0.0.3 and 10.0.0.4 have disappeared _without_
> > any notification.
>
> Flushes do not generate notifications. The reason is technical: they
> are usually massive, do overflow buffer, get lost and listeners have
> to do painful resynchronization. The justification: they are useless
> because these events are derived.
I perfectly agree, still I'm not happy with deleting the local routes
for the temporarly orphaned secondaries without notifications and
just re-add them again later.
I think we should either prevent the deletion of the local routes by
rewriting their preferred source address during promotion or explicitely
announce the temprary orphaned secondaries as down and up again in order
to have the local routes deleted/re-added in a clean way.
prev parent reply other threads:[~2005-11-05 19:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 18:46 [PATCH] [IPV4] Fix secondary IP addresses after promotion Brian Pomerantz
2005-11-05 0:34 ` Patrick McHardy
2005-11-05 0:58 ` Brian Pomerantz
2005-11-05 1:07 ` Thomas Graf
2005-11-05 1:21 ` Patrick McHardy
2005-11-05 4:28 ` Patrick McHardy
2005-11-05 13:46 ` Thomas Graf
2005-11-07 21:50 ` Thomas Graf
2005-11-08 14:11 ` Patrick McHardy
2005-11-09 0:56 ` Thomas Graf
2005-11-11 13:16 ` Patrick McHardy
2005-11-16 19:21 ` Brian Pomerantz
2005-11-05 18:39 ` Alexey Kuznetsov
2005-11-05 19:06 ` Thomas Graf [this message]
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=20051105190636.GU23537@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=bapper@piratehaven.org \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@coreworks.de \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--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).