From: Andrea G Forte <andreaf@cs.columbia.edu>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Hasso Tepper <hasso@estpak.ee>,
Harald Welte <laforge@gnumonks.org>,
Neil Horman <nhorman@redhat.com>,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: primary and secondary ip addresses
Date: Fri, 17 Dec 2004 12:17:48 -0500 [thread overview]
Message-ID: <41C314BC.3060507@cs.columbia.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0412171736210.17463@filer.marasystems.com>
> How it works today is that the first IP you add in a subnet becomes a
> primary, any additional IPs you add in the same subnet becomes
> secondary. You can have any number of primary IPs with each any number
> of secondary IPs, the primary IPs just can't be in the same subnet.
>
Well, when I assign a new IP (for a new subnet) to the same interface
(using ip route add...), even though the routing table is updated, it
still takes about 500ms for the change to happen. This new IP should be
detected as primary, right? Also, am I right to say that any IP address
assigned to an alias interface is a secondary IP?
Do you know where the code for the routing cache is?
Thanks for your help,
Andrea
> Regards
> Henrik
next prev parent reply other threads:[~2004-12-17 17:17 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 [this message]
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=41C314BC.3060507@cs.columbia.edu \
--to=andreaf@cs.columbia.edu \
--cc=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).