netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hasso Tepper <hasso@estpak.ee>
To: Harald Welte <laforge@gnumonks.org>
Cc: Henrik Nordstrom <hno@marasystems.com>,
	Neil Horman <nhorman@redhat.com>,
	linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: primary and secondary ip addresses
Date: Thu, 16 Dec 2004 11:53:51 +0200	[thread overview]
Message-ID: <200412161153.51251.hasso@estpak.ee> (raw)
In-Reply-To: <20041216092831.GO2862@sunbeam.de.gnumonks.org>

Harald Welte wrote:
> [Cc'ing netdev, since nobody replied since november]
> On Wed, Nov 10, 2004 at 12:38:19AM +0100, Henrik Nordstrom wrote:
> > A more valid question is why one can not add more than one primary in
> > the same subnet.
> >
> > ip addr add x.x.x.x/y dev eth0 primary
> >
> > would make sense to me, clearly indicating that these addresses are
> > maintained separately.
>
> agreed.

And why I can't even choose which address is primary?

> > or put in another way why the addresses automatically become secondary
> > addresses to the first added address.
>
> ... and why does removing the primary address remove all secondary
> addresses.  This makes it complicated if you have one interface with
> multiple ip addresse, that change over time (failover, let's say.)  You
> don't know yet, which address you need to remove, because you don't know
> which of your peers fails.
>
> So you have all this complicated userspace magic that checks whether the
> address that is about to be deleted is the primary, and if yes, re-add
> all the other addresses.  If if is a secondary, you're happy and only
> need to delete that one.
>
> Can anyone comment what the idea of all this was?

This reminds me related issue ... Actually there is concept in Junos 
software I'd love to see in Linux as well. There is "preferred address" and 
"primary address" in Junos. Quoting Junos documentation:

**************************************************************************

Primary
=======

Configure this address to be the primary address of the protocol on 
the interface. If the logical unit has more than one address, the 
primary address is used by default as the source address when packets 
originate from the interface and the destination does not indicate 
the subnet (ie. multicast destination for example). 

Default

For unicast traffic, the primary address is the lowest non-127
preferred address on the unit.

Preferred
=========

Configure this address to be the preferred address on the interface. 
If you configure more than one address on the same subnet, the 
preferred source address is chosen by default as the source address 
when you originate packets to destinations on the subnet. 

Default

The lowest numbered address on the subnet is the preferred address.
**************************************************************************

Would it be overkill for Linux? From the routers point of view it does make 
perfect sense. And of course you can manually override defaults in Junos.


-- 
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator

  reply	other threads:[~2004-12-16  9:53 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 [this message]
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
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=200412161153.51251.hasso@estpak.ee \
    --to=hasso@estpak.ee \
    --cc=hno@marasystems.com \
    --cc=laforge@gnumonks.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=nhorman@redhat.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).