From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] additional routes?
Date: Thu, 28 Nov 2002 22:32:34 +0000 [thread overview]
Message-ID: <marc-lartc-103852305321535@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103849751630293@msgid-missing>
(Forwarded to the list because I can't properly operate a MUA--maybe
they'll take away my license to read email someday.)
Tomas,
Perhaps you want a summary of how the kernel makes a routing decision?
See my description of the route selection process:
http://plorf.net/linux-ip/html/routing-selection.htm
I'm not sure you need policy routing though... If network B is reachable
from network A, and the router for network B is directly connected to
network A but is not the default gateway, you'll have something sort of
like this:
network-C via router-B
network-B via router-B
network-A dev ethX
default via default-gw
Is this your configuration? If so, then you need no policy routing.
-Martin
On Thu, 28 Nov 2002, Tomas Bonnedahl wrote:
: hello, a simple question; on a router, if I want network A to be routed
: to network C that goes through network B, using policy routing, do i
: need to specify a route to network B also, or could i just have routes
: to A and C in the routing table?
:
: the reason that im asking is because i dont know how the ip utility
: uses the main table together with antoher table. if i didnt use policy
: routing, just "regular", this would not work, but perhaps if not
: finding a route to network B, it checks the main table?
:
:
: please enlighten me.
:
: regards,
:
: tomas bonnedahl
: _______________________________________________
: LARTC mailing list / LARTC@mailman.ds9a.nl
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-28 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 15:30 [LARTC] additional routes? Tomas Bonnedahl
2002-11-28 22:32 ` Martin A. Brown [this message]
2002-11-28 23:35 ` Tomas Bonnedahl
2002-11-29 5:48 ` Martin A. Brown
2002-11-29 7:39 ` Tomas Bonnedahl
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=marc-lartc-103852305321535@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.