From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: two subnets...
Date: Tue, 31 Jul 2007 15:07:48 -0500 [thread overview]
Message-ID: <46AF9694.1060709@riverviewtech.net> (raw)
In-Reply-To: <46AF8D63.8080900@interia.pl>
On 07/31/07 14:28, Pawel Zawora wrote:
> I need separate 3 foreign machines (security reason - firewall
> between subnets is required).
*nod* This is not a problem at all.
> I cannot divide one 128 pubic IPs subnet...
You do not need to.
> Foreign machines have to use public IPs....
*nod*
Say you have the following systems:
+---------+
| a.b.c.1 +---+
+---------+ |
| a.b.c.3 +---+
+---------+ |
| a.b.c.5 +---+
+---------+ | +--------+
| a.b.c.7 +---+---+ Router +---(Internet)
+---------+ | +--------+
| a.b.c.9 +---+
+---------+ |
| a.b.c.8 +---+
+---------+ |
| a.b.c.6 +---+
+---------+
And you want to split some of the computers off on to their own segment
so that they can not talk to the others and others can not talk to them.
+---------+
| a.b.c.1 +---+
+---------+ |
| a.b.c.3 +---+
+---------+ |
| a.b.c.5 +---+
+---------+ |
| a.b.c.7 +---+---+
+---------+ | +-------------------------------+
+---+ |
======================| Bridge / OSI Layer 2 Firewall +---(Internet)
+---+ |
+---------+ | +-------------------------------+
| a.b.c.9 +---+---+
+---------+ |
| a.b.c.8 +---+
+---------+ |
| a.b.c.6 +---+
+---------+
Let's assume that:
- eth0 (top) goes to the top set of computers
- eth1 (middle) goes to the internet
- eth2 (bottom) goes to the bottom set of computers
Add eth0 and eth2 to the bridge.
Allow all traffic to pass through the bridge by default.
Block traffic from coming in to the bridge from eth0 and going out eth2.
Block traffic from coming in to the bridge from eth2 and going out eth0.
This allows traffic to come in eth0 and go out eth1.
This allows traffic to come in eth1 and go out either eth0 or eth2.
This allows traffic to come in eth2 and go out eth1.
This prevents computers on either part of the bridge from talking with
each other. Thus your computers that you can not change the IP
addresses on are still at the same IP address.
This allows you to have two logically separated LANs so that they can
not communicate with each other.
Does this help explain what I'm talking about? Again, I have used this
scenario MANY MANY times and have been EXTREMELY pleased with it. Let
me know if I need to try to explain this differently.
If this is what you are wanting to do, EBTables can VERY easily
accomplish this. Let me know if this is what you need and I'll help
provide you with a mach EBTables set up.
Grant. . . .
next prev parent reply other threads:[~2007-07-31 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 10:31 two subnets Pawel
2007-07-31 15:05 ` Grant Taylor
2007-07-31 19:28 ` Pawel Zawora
2007-07-31 20:07 ` Grant Taylor [this message]
2007-07-31 22:40 ` Mike Wright
2007-07-31 23:28 ` Grant Taylor
2007-08-01 13:38 ` Maximilian Wilhelm
2007-08-01 14:04 ` Pascal Hambourg
2007-08-01 20:14 ` Pawel Zawora
2007-08-01 21:14 ` Grant Taylor
2007-08-01 22:44 ` Pawel Zawora
2007-08-02 1:11 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 19:15 Pawel Zawora
[not found] <200708020115.l721FOEu011164@mail3.jubileegroup.co.uk>
2007-08-02 5:56 ` G.W. Haywood
2007-08-02 14:14 ` Michael P. Brininstool
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=46AF9694.1060709@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=gtaylor+reply@riverviewtech.net \
--cc=netfilter@lists.netfilter.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