From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: blocking traffic between two internal interfaces ?
Date: Wed, 19 Oct 2005 22:40:12 -0500 [thread overview]
Message-ID: <200510192240.12970.rob0@gmx.co.uk> (raw)
In-Reply-To: <20051020030747.A4016F6F2@sorry.no-ip-here.net>
On Wednesday 2005-October-19 22:07, Seferovic Edvin wrote:
> I have two internal interfaces ( eth1 // 172.19.0.0 & eth2 //
> 172.20.0.0 ), and I would like to block traffic between those two
> networks. Somehow Ive failed because any rules that should forbid
> traffic between those 2 networks didn't work. I still could access
> webserver on the eth2 - 172.20.10.1 from a station with IP address
> 172.19.1.100 ! Then Ive applied rule in PREROUTING chain in nat
Thou shalt not filter in the nat table.
> Iptables -t nat -A PREROUTING -s 172.19.0.0/16 -d 172.20.0.0/16 -j
> DROP
I would use interfaces, not IP addresses.
> Rules in FORWARD and INPUT chain just wouldn't work. Is this the
What did you try in FORWARD?
> right way to forbid traffic from one network to the another or am I
> missing some basic stuff here? I would appreciate any comments.
In FORWARD, block incoming on eth1 going to eth2 and vice versa.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next parent reply other threads:[~2005-10-20 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051020030747.A4016F6F2@sorry.no-ip-here.net>
2005-10-20 3:40 ` /dev/rob0 [this message]
2005-10-20 4:11 ` blocking traffic between two internal interfaces ? Seferovic Edvin
[not found] <20051020052237.E5BB0F4DA@sorry.no-ip-here.net>
2005-10-20 13:27 ` /dev/rob0
[not found] <20051020041130.0D02EF6F2@sorry.no-ip-here.net>
2005-10-20 4:32 ` /dev/rob0
2005-10-20 5:22 ` Seferovic Edvin
2005-10-20 3:07 Seferovic Edvin
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=200510192240.12970.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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