From: Christian Seberino <seberino@spawar.navy.mil>
To: "James T. Moore" <jamoore2@vt.edu>
Cc: netfilter@lists.samba.org
Subject: Re: how is this stuff getting thru default deny iptables firewall?....
Date: Sun, 23 Jun 2002 00:13:59 -0700 [thread overview]
Message-ID: <20020623001359.B949@spawar.navy.mil> (raw)
In-Reply-To: <000701c21a35$d5b51b00$0264a8c0@ZANE>; from jamoore2@vt.edu on Sat, Jun 22, 2002 at 05:43:22PM -0400
James
Thanks, I sent rule set to thread in another email.
I don't have anything with ESTABLISHED or RELATED in it.
Chris
On Sat, Jun 22, 2002 at 05:43:22PM -0400, James T. Moore wrote:
> Chris,
>
> My guess would be that the firewall is allowing reponses to connections
> that are already established, but its impossible to say for sure without
> seeing the script used to create the firewall.
>
> Here is an example:
>
> $IPTABLES -A FORWARD -o $INET_IFACE -d $DNS_SERV1 -s $PRIV_LAN -p
> udp --dport 53 -m state --state NEW,ESTABLISHED -j ACCEPT
>
> $IPTABLES -A FORWARD -i $INET_IFACE -s $DNS_SERV1 -d $PRIV_LAN -p
> udp --sport 53 -m state --state ESTABLISHED -j ACCEPT
>
>
> The first rule allows the clients on the private LAN to query the dns
> server. These packets can be part of a new or established connection so the
> clients can create new connections to connect to the DNS server.
>
> The second rule allows the DNS server to respond to the clients' request.
> These packets can only be part of an established connection so the DNS
> server (or any other host) can not create a new connection into the private
> LAN unless there are other rules to allow it.
>
>
> J.T.
>
>
>
>
> >Date: Sat, 22 Jun 2002 10:30:55 -0700
> >From: Christian Seberino <seberino@spawar.navy.mil>
> >To: netfilter@lists.samba.org
> >Subject: how is this stuff getting thru default deny iptables firewall?....
> >
> >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??!?!?!?
> >
> >Chris
--
_______________________________________
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 21:43 how is this stuff getting thru default deny iptables firewall? James T. Moore
2002-06-23 7:13 ` Christian Seberino [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-06-22 17:30 Christian Seberino
2002-06-22 17:38 ` Antony Stone
2002-06-23 7:13 ` Christian Seberino
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
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=20020623001359.B949@spawar.navy.mil \
--to=seberino@spawar.navy.mil \
--cc=jamoore2@vt.edu \
--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