From: Thomas Graf <tgraf@suug•ch>
To: Harald Welte <laforge@gnumonks•org>
Cc: jamal <hadi@cyberus•ca>, Henrik Nordstrom <hno@marasystems•com>,
"David S. Miller" <davem@davemloft•net>,
Andrea G Forte <andreaf@cs•columbia.edu>,
hasso@estpak•ee, nhorman@redhat•com, linux-net@vger•kernel.org,
netdev@oss•sgi.com
Subject: Re: primary and secondary ip addresses
Date: Sun, 19 Dec 2004 23:02:11 +0100 [thread overview]
Message-ID: <20041219220211.GQ17998@postel.suug.ch> (raw)
In-Reply-To: <20041219214120.GX17302@sunbeam.de.gnumonks.org>
* Harald Welte <20041219214120.GX17302@sunbeam•de.gnumonks.org> 2004-12-19 22:41
> On Sun, Dec 19, 2004 at 03:18:37PM -0500, jamal wrote:
>
> > Having said the above, I think it would make sense to have a "promotion"
> > scheme so that in the case a primary address is deleted, one could
> > promote the next secondary address in line. But that should be optional.
>
> Oh yes, please. This would save a lot of headache. I'm much in favour
> of such a proposal.
Agreed, would be nice to have.
> > Now where is the fireman who wants to do this? I could help cheering
> > since i know the code.
>
> how would you think it fits best into the current netlink messages?
1) IFA_F_PROM_CAND flag and have inet_del_ifa* iterate over its
secondary addresses and elect the first with the flag set.
2) IFA_PROM_PRIO TLV of type u32 holding a priority where 0 means no
candiate. inet_del_ifa* iterates over its secondary addresses and
elects the one with the highest prio as new primary address or
deletes all addresses if none is found.
* respectively the equivalent function of the other address families.
Second variant requires more work but is more flexible so it's
definitely my favourite. I'm willing to put some effort into this,
I'm not familiar with all address families though.
next prev parent reply other threads:[~2004-12-19 22:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41912F7A.6000408@redhat.com>
[not found] ` <Pine.LNX.4.61.0411100034320.10593@filer.marasystems.com>
2004-12-16 9:28 ` primary and secondary ip addresses Harald Welte
2004-12-16 9:53 ` Hasso Tepper
2004-12-16 10:07 ` Henrik Nordstrom
2004-12-16 11:02 ` Hasso Tepper
2004-12-16 16:02 ` Henrik Nordstrom
2004-12-17 15:10 ` Andrea G Forte
2004-12-17 15:27 ` Henrik Nordstrom
2004-12-17 15:58 ` Andrea G Forte
2004-12-17 16:39 ` Henrik Nordstrom
2004-12-17 17:17 ` Andrea G Forte
2004-12-17 19:17 ` Henrik Nordstrom
2004-12-17 18:03 ` Hasso Tepper
2004-12-17 18:37 ` Martin A. Brown
2004-12-17 18:53 ` Hasso Tepper
2004-12-17 19:25 ` Henrik Nordstrom
2004-12-17 20:55 ` Hasso Tepper
2004-12-17 20:54 ` Andrea G Forte
2004-12-17 19:20 ` David S. Miller
2004-12-17 19:48 ` Henrik Nordstrom
2004-12-19 20:18 ` jamal
2004-12-19 21:41 ` Harald Welte
2004-12-19 22:02 ` Thomas Graf [this message]
2004-12-19 22:59 ` jamal
2004-12-19 23:56 ` jamal
2004-12-20 13:55 ` jamal
2004-12-20 14:29 ` Harald Welte
2005-04-12 10:54 ` Harald Welte
2005-05-08 12:31 ` Hasso Tepper
2005-05-26 18:11 ` Harald Welte
2005-05-26 18:21 ` Thomas Graf
2005-05-26 21:58 ` David S. Miller
2004-12-16 16:48 ` Paul Jakma
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=20041219220211.GQ17998@postel.suug.ch \
--to=tgraf@suug$(echo .)ch \
--cc=andreaf@cs$(echo .)columbia.edu \
--cc=davem@davemloft$(echo .)net \
--cc=hadi@cyberus$(echo .)ca \
--cc=hasso@estpak$(echo .)ee \
--cc=hno@marasystems$(echo .)com \
--cc=laforge@gnumonks$(echo .)org \
--cc=linux-net@vger$(echo .)kernel.org \
--cc=netdev@oss$(echo .)sgi.com \
--cc=nhorman@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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