From: Christian Seberino <seberino@spawar.navy.mil>
To: Julian Gomez <kluivert@tm.net.my>
Cc: netfilter@lists.samba.org
Subject: Re: how is this stuff getting thru default deny iptables firewall?....
Date: Wed, 10 Jul 2002 09:34:18 -0700 [thread overview]
Message-ID: <20020710093418.A27977@spawar.navy.mil> (raw)
In-Reply-To: <Pine.LNX.4.33.0207101903030.1723-100000@dodobirdy.nestac.com>; from kluivert@tm.net.my on Wed, Jul 10, 2002 at 07:03:55PM +0800
> ipchains is a simple packet filter. it looks at per packet header
> information and passes that through the ruleset for analysis and whether
> it gets forwarded or not.
>
> there is no 'keeping of header info' unlike iptables which is stateful.
Thanks for the help. I think this must be right. However, can you
explain the mechanism that allows a PC on the private LAN to
do DNS, HTTP, etc. thru an SSH-only ipchains firewall???
The *must* be *some* mechanism to allow return packets of an
existing TCP connection to bypass firewall!
CS
next prev parent reply other threads:[~2002-07-10 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 19:43 how is this stuff getting thru default deny iptables firewall? 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 [this message]
-- 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-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=20020710093418.A27977@spawar.navy.mil \
--to=seberino@spawar.navy.mil \
--cc=kluivert@tm.net.my \
--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