From: "Daniel L. Miller" <dmiller@amfes.com>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Basic Routing
Date: Mon, 20 Sep 2010 14:40:06 -0700 [thread overview]
Message-ID: <4C97D4B6.2000609@amfes.com> (raw)
In-Reply-To: <4911D85E.2080109@riverviewtech.net>
On 11/5/2008 9:31 AM, Grant Taylor wrote:
> 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*
>
>> 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. :)
>
>
Once upon a time I asked this list some routing questions. I've almost
got it - I swear I've ALMOST got it. One more little push and I think
I'm there.
Given the specific architecture:
Windows Workstation 192.168.5.100, default gateway 192.168.5.1
Linux Gateway/Router/VPN node 192.168.7.2, 192.168.5.1, 192.168.0.90,
default gateway 192.168.7.1
DSL Modem 192.168.7.1
Linux Server/Router/VPN server/Virtual Server 192.168.0.71,
192.168.56.1, default gateway 192.168.0.1
Virtual Machine 192.168.56.20, default gateway 192.168.56.1
What is the "easiest" way of "achieving routing" between the Windows
Workstation and the Virtual Machine? Is this an instance where NAT
would make administration simpler instead of "pure" routing? The
cumbersome-but-working method I have employed at the moment includes;
add 192.168.56.0/24 via 192.168.0.71 route to Workstation
add 192.168.56.0/24 via 192.168.0.71 route to Linux Gateway
add 192.168.5.0/24 via 192.168.0.90 route to Linux Server
I almost understand the need for the 192.168.5.0/24 entry on the Linux
Server side - because otherwise the router doesn't know how to reply,
and the same goes for the 192.168.56.0/24 entry on the Gateway side -
otherwise the Gateway doesn't know how to reach that subnet in the first
place. But, if the Gateway is defined as the default for the
Workstation, why is a routing entry required for the Workstation?
--
Daniel
next prev parent reply other threads:[~2010-09-20 21:40 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
2010-09-20 21:40 ` Daniel L. Miller [this message]
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=4C97D4B6.2000609@amfes.com \
--to=dmiller@amfes.com \
--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).