From: Christian Seberino <seberino@spawar.navy.mil>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter@lists.samba.org
Subject: Re: how is this stuff getting thru default deny iptables firewall?....
Date: Sun, 23 Jun 2002 00:13:02 -0700 [thread overview]
Message-ID: <20020623001302.A949@spawar.navy.mil> (raw)
In-Reply-To: <20020622173842.AGM19225.mta07-svc.ntlworld.com@there>; from Antony@Soft-Solutions.co.uk on Sat, Jun 22, 2002 at 06:38:40PM +0100
Antony
Thanks again.
Here is my rule set... it is preceded by the usual stuff
like flushing chains, dropping certain classes of packets, etc.
These are the *only* rules with "-j ACCEPT" in my entire firewall script
and somehow DNS sneaks thru...
$PROTECTED_NETWORK = 192.168.0.0/29
$PROTECTED_NETWORK_SPACE = 192.168.0.0/16
...
# Allow all thru loopback.
$IPTABLES -t filter -A INPUT -i $LOOPBACK_INTERFACE -j ACCEPT
$IPTABLES -t filter -A OUTPUT -o $LOOPBACK_INTERFACE -j ACCEPT
# Only SSH from Internet but anything *to* Internet.
$IPTABLES -t filter -A FORWARD -i $INTERNET_INTERFACE \
-s ! $PROTECTED_NETWORK_SPACE -d $PROTECTED_PC_IP_ADDRESS \
-p tcp --dport $SSH_PORT \
-j ACCEPT
$IPTABLES -t filter -A FORWARD -o $INTERNET_INTERFACE \
-s $PROTECTED_NETWORK -d ! $PROTECTED_NETWORK_SPACE \
-j ACCEPT
# Allow all thru priviate LAN NIC.
$IPTABLES -t filter -A FORWARD -i $PROTECTED_NETWORK_INTERFACE \
-s $PROTECTED_NETWORK -d ! $PROTECTED_NETWORK_SPACE \
-j ACCEPT
$IPTABLES -t filter -A FORWARD -o $PROTECTED_NETWORK_INTERFACE \
-s ! $PROTECTED_NETWORK_SPACE -d $PROTECTED_NETWORK \
-j ACCEPT
# The usual NAT stuff here.
$IPTABLES -t nat -A PREROUTING -i $INTERNET_INTERFACE \
-s ! $PROTECTED_NETWORK_SPACE -d $INTERNET_IP_ADDRESS \
-p tcp --dport $SSH_PORT \
-j DNAT --to-destination $PROTECTED_PC_IP_ADDRESS
$IPTABLES -t nat -A POSTROUTING -o $INTERNET_INTERFACE \
-s $PROTECTED_NETWORK -d ! $PROTECTED_NETWORK_SPACE \
-j SNAT --to-source $INTERNET_IP_ADDRESS
I don't have *anything* with ESTABLISHED or RELATED that would allow
DNS to sneak in...... *but it does*!?!?!?!?
Chris
On Sat, Jun 22, 2002 at 06:38:40PM +0100, Antony Stone wrote:
> On Saturday 22 June 2002 6:30 pm, Christian Seberino wrote:
>
> > My firewall *only* forwards SSH stuff to private LAN.
> >
> > It forwards *everything* _from_ private LAN to Internet however.
> >
> > How can the private LAN use DNS which it does????
> >
> > How is DNS server returning the info thru firewall
> > if it *only* allows SSH??!?!?!?
>
> Do you have a rule allowing reply packets from, say, a website back to your
> internal clients ?
>
> Maybe:
>
> iptables -A FORWARD -i $EXTIF -m state --state RELATED,ESTABLISHED -j ACCEPT
>
> Same rule will allow replies to DNS requests.
>
> If you don't have anything like that, post your ruleset and we'll have a
> think about it.
>
>
>
> Antony.
--
_______________________________________
Dr. Christian Seberino
SPAWAR Systems Center San Diego
Code 2363
53560 Hull Street
San Diego, CA 92152-5001
U.S.A.
Phone: (619) 553-7940
Fax: (619) 553-2836
Email: seberino@spawar.navy.mil
_______________________________________
next prev parent reply other threads:[~2002-06-23 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-22 17:30 how is this stuff getting thru default deny iptables firewall? Christian Seberino
2002-06-22 17:38 ` Antony Stone
2002-06-23 7:13 ` Christian Seberino [this message]
2002-06-23 7:53 ` Patrick Schaaf
2002-06-27 7:21 ` Christian Seberino
2002-06-27 7:37 ` Patrick Schaaf
2002-07-09 19:08 ` Christian Seberino
2002-06-23 8:07 ` Antony Stone
2002-06-27 7:14 ` Christian Seberino
2002-06-27 7:28 ` Patrick Schaaf
-- strict thread matches above, loose matches on Subject: below --
2002-06-22 21:43 James T. Moore
2002-06-23 7:13 ` Christian Seberino
2002-07-09 19:43 j davis
2002-07-09 21:41 ` Christian Seberino
2002-07-09 21:43 ` Christian Seberino
[not found] ` <Pine.LNX.4.33.0207101903030.1723-100000@dodobirdy.nestac.com>
2002-07-10 16:34 ` Christian Seberino
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=20020623001302.A949@spawar.navy.mil \
--to=seberino@spawar.navy.mil \
--cc=Antony@Soft-Solutions.co.uk \
--cc=netfilter@lists.samba.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