netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Basic Routing
Date: Wed, 05 Nov 2008 11:31:10 -0600	[thread overview]
Message-ID: <4911D85E.2080109@riverviewtech.net> (raw)
In-Reply-To: <49119087.5060307@thehaxbys.co.uk>

On 11/05/08 06:24, John Haxby wrote:
> Perhaps the problem is that the good people on this list know just 
> too much about the finer points of routing and the caveats and 
> wrinkles that you occasionally need to avoid special purpose 
> problems.

*nod* (guilty) *nod*

> For the most part, though, it's actually quite simple.   And I know 
> that some of the things I will say are wrong in some cases and I 
> would hope that someone will explain to me where they're wrong and 
> maybe we'll all be enlightened.

I don't see any thing wrong with what you have said.  I might have used 
different wording, but we are two different humans.  :)

<snip>

I do have a quick comment to add about the routing table though.  The 
routing table is ordered with the most specific match first (what you 
were getting at by the number of zeros).  So when the routing table is 
searched, the first route to be found, the most specific one, is the 
proper one.  The reason you might have a more specific route and a less 
specific route is if you have a fast high latency satellite connection 
to and a slow low latency dial up or leased line connection back to 
corporate.  You would want the bulk of (non interactive) traffic to go 
through the faster high latency connection for most things but still 
have smaller interactive (think terminal type) traffic go over the 
slower lower latency dial up / leased line.  To be able to do this you 
would put the destination server equipment for the interactive traffic 
be in a smaller ""special part of the larger address range.  Then you 
tell the router that it has access to the smaller range over the dial up 
and the rest of the address range across the satellite.

The more specific routes can be used to override less specific routes.

> Does that help or has it left you even more confused?

I'm guessing that it left Daniel with more to think about and to 
formulate more questions.  Which is in and of it self a good thing as 
that is the normal process of learning.  :)



Grant. . . .

  reply	other threads:[~2008-11-05 17:31 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 16:15 Basic Routing Daniel L. Miller
2008-11-02 17:03 ` Rob Sterenborg
2008-11-02 18:43   ` Daniel L. Miller
2008-11-02 19:53     ` Rob Sterenborg
2008-11-03  1:59       ` Daniel L. Miller
2008-11-02 20:04     ` Grant Taylor
2008-11-02 20:51     ` Grant Taylor
2008-11-03  1:52       ` Daniel L. Miller
2008-11-03  2:34         ` Grant Taylor
2008-11-03 19:29           ` Daniel L. Miller
2008-11-03 19:39             ` Daniel L. Miller
2008-11-03 20:26               ` Grant Taylor
2008-11-05  0:00                 ` Daniel L. Miller
2008-11-05  5:21                   ` Rob Sterenborg
2008-11-05 15:56                     ` Grant Taylor
2008-11-05 18:22                       ` Rob Sterenborg
2008-11-05 18:30                         ` Grant Taylor
2008-11-05 19:49                           ` Rob Sterenborg
2008-11-05 15:24                   ` Grant Taylor
2008-11-03 23:40               ` Amos Jeffries
2008-11-04 23:13             ` Grant Taylor
2008-11-04 23:53               ` Daniel L. Miller
2008-11-05 12:24                 ` John Haxby
2008-11-05 17:31                   ` Grant Taylor [this message]
2010-09-20 21:40                     ` Daniel L. Miller
2010-09-20 23:41                       ` Jan Engelhardt
2010-09-21  3:34                       ` Grant Taylor
2008-11-05 17:17                 ` Grant Taylor
2008-11-02 19:06   ` Grant Taylor
2008-11-03 10:54     ` Pascal Hambourg
2008-11-03 16:35       ` Grant Taylor
  -- strict thread matches above, loose matches on Subject: below --
2014-10-04  1:10 Basic routing John Smithee
2014-10-04  1:24 ` John Smithee
2014-10-04  8:50   ` George Botye
2014-10-04  1:34 ` Neal Murphy
2014-10-04  2:52   ` John Smithee
2014-10-04  3:05     ` Dennis Jacobfeuerborn
2014-10-04  5:02     ` Neal Murphy
2014-10-04  7:04     ` John Lister
2014-10-04 11:06       ` John Smithee
2014-10-04 13:56         ` Thomas Bätzler
2014-10-04 15:07           ` John Smithee
2014-10-04 17:44             ` John Smithee
2014-10-05 15:41               ` John Lister
2014-10-06  9:41               ` André Paulsberg

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=4911D85E.2080109@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@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 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).