From: "John A. Sullivan III" <jsullivan@opensourcedevelopmentcorp.com>
To: Mike <1100100@gmail.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: One Nic; Multiple Subnets
Date: Mon, 27 Dec 2004 12:01:42 -0500 [thread overview]
Message-ID: <1104166901.2008.51.camel@localhost> (raw)
In-Reply-To: <8ca4228204122708388845e28@mail.gmail.com>
I'm afraid I do not have time to answer in depth today but I'll try to
point you in the right direction.
On Mon, 2004-12-27 at 11:38, Mike wrote:
> I've been looking through the monthly archives of this list, but I
> can't find the needle in the haystack. I saw this question answered
> before, and I'm hoping I'll see it again. :-)
>
> I have an old slackware routerbox that only has room for 2 nics.
> Right now there are two nics. in it and they are set up like so:
>
> eth0 --> Internet (Dynamic IP: Assigned by ISP)
> eth1 --> Lan (Gateway Interface: 192.168.1.1)
>
> I will soon be joining some computers from another LAN into the one
> mentioned above.
> I will need to set up security measures so that the new computers will
> not be hacked or viewed by the other users on the LAN.
>
> Even though I've only got one C-Class subnet (192.168.1.1 - 255), I
> want to create 2 or more "virtual" subnets to reside in this address
> range.
>
> How do I create the multiple subnets?
You can break them into distinct subnets with subnet masking and bind
multiple addresses to the same NIC using iproute2 (the "ip" command).
> Do I need to use route command or ipsec.?
> And what would the iptables rule look like, where Subnet "B" rejects
> all packets coming from Subnet "A"?
>
> Is this even close? ---
> $IPTABLES -t filter FORWARD -A -i eth1 -s 192.168.1.2/150
> --to-destination 192.168.1.151/253 -j DENY
You've got the basic idea but both your syntax and your grasp of some
fundamental issues seems weak. I would suggest a tour of Oskar
Andreasson's iptables tutorial (you can find the link on the netfilter
web site (http://www.netfilter.org). You can also find some slide shows
on using iptables and iproute2 in the training section of the ISCS
network security management project page at http://iscs.sourceforge.net
You may also want to brush up on subnet masking.
I apologize that this isn't a cook book solution but it sounds like you
might be benefited by a little more information besides just the
recipe. Good luck - John
<snip>
--
John A. Sullivan III
Open Source Development Corporation
Financially sustainable open source development
http://www.opensourcedevel.com
next prev parent reply other threads:[~2004-12-27 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 18:30 Drop packets with low IP Time to Live field value Jorge Agrelo
2004-12-24 18:56 ` Jason Opperisano
2004-12-25 2:08 ` Chris Brenton
2004-12-27 15:25 ` Nick Drage
2004-12-27 16:38 ` One Nic; Multiple Subnets Mike
2004-12-27 16:52 ` Jason Opperisano
2004-12-27 17:57 ` Mike
[not found] ` <16365.213.236.112.75.1104237335.squirrel@213.236.112.75>
2004-12-28 17:35 ` Mike
2004-12-27 17:01 ` John A. Sullivan III [this message]
2004-12-27 17:43 ` Mike
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=1104166901.2008.51.camel@localhost \
--to=jsullivan@opensourcedevelopmentcorp.com \
--cc=1100100@gmail.com \
--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