From: "Rob Sterenborg" <rob@sterenborg.info>
To: netfilter@vger.kernel.org
Subject: RE: Basic Routing
Date: Wed, 5 Nov 2008 20:49:53 +0100 [thread overview]
Message-ID: <018301c93f7f$ac4cf190$04e6d4b0$@info> (raw)
In-Reply-To: <4911E661.2030505@riverviewtech.net>
> +---+ +---+ +---+ +---+
> | A +---(x)---+ C +---(y)---+ D +---(z)---+ B |
> +---+ +---+ +---+ +---+
>
> A knows about network x.
> C knows about networks x and y.
> D knows about networks y and z.
> B knows about network z.
>
> C does /not/ know about network z.
> D does /not/ know about network x.
Yes you're correct.. I should stop assuming things that I already
figured out in my head but don't write down when replying. (Actually, a
"few" emails ago I wrote an email that describes the exact same as the
above -including art- but I discarded it when I saw your answer which
was even more complete.)
> We have already covered the IP forwarding in another email. As far
> as the firewalling is concerned, you are correct. However I believe
> Daniel said that there was no firewalling (yet).
Nope, there was no word about firewalling, just NAT and routing.
> Agreed. I think both are likely good ways to learn about
> firewalling, specifically IPTables. Seeing as how this
> discussion is about routing...
We started with NAT, which is something that netfilter can do and what
the tutorial also describes, and routing. I was hoping that Daniel would
see why he didn't need NAT by reading it.
Daniel, this is getting lengthy and I think everything that needed to be
said has been said about NAT and routing. I hope things are (more) clear
now.
Grts,
Rob
next prev parent reply other threads:[~2008-11-05 19:49 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 [this message]
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
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='018301c93f7f$ac4cf190$04e6d4b0$@info' \
--to=rob@sterenborg.info \
--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).