From: Payal Rathod <payal-netfilter@scriptkitchen.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: LAN accessing DMZ
Date: Sun, 18 Jul 2004 12:58:30 -0400 [thread overview]
Message-ID: <20040718165830.GA30303@tranquility.scriptkitchen.com> (raw)
In-Reply-To: <200407181739.05377.Antony@Soft-Solutions.co.uk>
On Sun, Jul 18, 2004 at 05:39:05PM +0100, Antony Stone wrote:
> This one:
> > > > $IPTABLES -A FORWARD -d 10.10.10.2 -p tcp --dport 25 -j ACCEPT
I have pasted my FORWARD rules at, (they are small and simple),
http://payal.staticky.com/fw1.txt
> > > > $IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> > > > $IPTABLES -A FORWARD -s 192.168.0.0/16 -p tcp --dport 3128 -j ACCEPT
> > > > $IPTABLES -A FORWARD -s 192.168.0.0/16 -p tcp --dport 53 -j ACCEPT
> > > > $IPTABLES -A FORWARD -s 192.168.0.0/16 -p udp --dport 53 -j ACCEPT
>
> These rules do not say "but only to the Internet", therefore they allow
> packets to the DMZ as well.
It is still very confusing. Forget port 25 for a moment. I have never
mentioned port 10000, the webmin port at all. Still I can access it
from my LAN machine? HOW? Afterall the FORWARD policy is DROP. It should
DROP what it cannot find.
If I do a specific DROP like
$IPTABLES -A FORWARD -s 192.168.0.0/16 -p tcp --dport 10000 -j DROP
the packets are dropped, but not otherwise.
What must be wrong?
With warm regards,
-Payal
next prev parent reply other threads:[~2004-07-18 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 13:23 LAN accessing DMZ Payal Rathod
2004-07-18 15:10 ` Antony Stone
2004-07-18 16:24 ` Payal Rathod
2004-07-18 16:39 ` Antony Stone
2004-07-18 16:58 ` Payal Rathod [this message]
2004-07-18 17:12 ` Antony Stone
2004-07-18 17:39 ` Payal Rathod
2004-07-18 17:59 ` Antony Stone
2004-07-18 18:51 ` Payal Rathod
2004-07-18 19:12 ` Antony Stone
2004-07-19 11:13 ` Payal Rathod
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=20040718165830.GA30303@tranquility.scriptkitchen.com \
--to=payal-netfilter@scriptkitchen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.