From: Hasso Tepper <hasso@estpak.ee>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: "Martin A. Brown" <mabrown@securepipe.com>,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: primary and secondary ip addresses
Date: Fri, 17 Dec 2004 22:55:21 +0200 [thread overview]
Message-ID: <200412172255.21316.hasso@estpak.ee> (raw)
In-Reply-To: <Pine.LNX.4.61.0412172021190.18385@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Fri, 17 Dec 2004, Hasso Tepper wrote:
> > All these tricks don't help if you are using dynamic routing.
>
> Are you seriously saying you are doing dynamic routing for your locally
> attached lans?
>
> source address assignment for routed traffic via gateways is
> automatically derived by the source address assignment for traffic
> addressed to the gateway itself.
So? Router learns via rip that default route should go via 10.0.0.1 and it
has 10.0.0.2/24 and 10.0.0.3/24 addresses on eth0.
> So even with routing protocols etc you
> can control the source address assignment simply by setting up routing to
> use the correct source address to speak to your gateways, the added
> routes will then inherit the intended source address.
No. It would be true in very trivial case only - ie. "use address I'm using
for announcing these routes as gateway for these routes". All routing
protocols can carry nexthop information. Moreover, addresses routing
protocols use for transport don't have to have anything common with
addresses used for routing. You can even carry IPv4 routing info with
routing protocol using IPv6 for transport (ospfv3) or iso (is-is).
--
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator
next prev parent reply other threads:[~2004-12-17 20:55 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 [this message]
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=200412172255.21316.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=hno@marasystems.com \
--cc=linux-net@vger.kernel.org \
--cc=mabrown@securepipe.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).