From: Chris <mlists@aon.at>
To: Matthew Hellman <mhellman@raccoon.com>
Cc: Hard__warE <hard__ware@hotmail.com>, netfilter@lists.samba.org
Subject: Re: Flag SYN not necessarily state NEW?
Date: Sat, 15 Jun 2002 16:52:03 +0200 [thread overview]
Message-ID: <3D0B5493.AA326DCB@aon.at> (raw)
In-Reply-To: 002001c21468$d4683a70$020aa8c0@matttm9svd8lrh
Matthew Hellman wrote:
> I must not be understanding what you're saying here, because you
> definitely need both a NEW and ESTABLISHED rule. In fact, this should
> always apply and I would be rather disappointed in netfilter if there
> were any exceptions. Don't think you need a RELATED rule however (at
< least it seems to function without one). FWIW to the original poster,
> I log incoming NEW ssh connections and it has always worked and still
> does. If I connect twice, it logs it twice. kernel version: 2.4.18,
> iptables version: 1.2.6a.
I have to excuse my question from 8.5., it was at a time where i just
started to play around with iptables (used ipchains before).
My posting came very delayed to this mailing-list (more than a month),
and in the meanwhile i can't "reproduce" this behaviour anymore. So i
think it was just a mistake on my side (wrong logging or whatever, some
mistake of a beginner :)).
regards, Chris
next prev parent reply other threads:[~2002-06-15 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 2:35 Flag SYN not necessarily state NEW? Hard__warE
2002-06-15 12:33 ` Matthew Hellman
2002-06-15 14:52 ` Chris [this message]
2002-06-15 12:35 ` default gateway problem Kumar
2002-06-15 12:48 ` Antony Stone
2002-06-15 21:57 ` Flag SYN not necessarily state NEW? Jozsef Kadlecsik
2002-06-16 18:04 ` Geog Hofstetter
2002-06-16 18:30 ` Antony Stone
2002-06-16 19:20 ` [x] - " Geog Hofstetter
[not found] <20020507115906.8B112471A@lists.samba.org>
2002-05-08 6:45 ` Ing. Christian Ogris
2002-06-14 11:17 ` Jozsef Kadlecsik
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=3D0B5493.AA326DCB@aon.at \
--to=mlists@aon.at \
--cc=hard__ware@hotmail.com \
--cc=mhellman@raccoon.com \
--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