From: Andrew Kolt <andrew_kolt@darkarts.no-ip.org>
To: netfilter@vger.kernel.org
Subject: state ESTABLISHED, RELATED
Date: Wed, 15 Jul 2009 23:25:39 +0300 [thread overview]
Message-ID: <4A5E3B43.4050408@darkarts.no-ip.org> (raw)
Hello everybody. I lately found my kernel logfile to be flooded with
connections that seemed to have no meaning.
They did until a couple of days ago when, while running nmap on a
computer on my network, i 'tailed' the logfile and discovered they were
replies from the target computer to my request.
As a temp solution i added the following to the INPUT chain, in order to
let those replies in:
-A INPUT -i eth0 -p tcp -s 0/0 -d zzz.zzz.zzz.zzz -m state --state
ESTABLISHED,RELATED -j ACCEPT
Everything works well now, but i'd like to know if there's any other way
to go about this and if the line above is "good" practice as far
as security goes.
with regards,
Andrew
next reply other threads:[~2009-07-15 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:25 Andrew Kolt [this message]
2009-07-16 6:42 ` state ESTABLISHED, RELATED Simion Onea
2009-07-16 8:21 ` Richard Horton
2009-07-16 8:54 ` Simion Onea
2009-07-16 8:32 ` Andrew Kolt
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=4A5E3B43.4050408@darkarts.no-ip.org \
--to=andrew_kolt@darkarts.no-ip.org \
--cc=netfilter@vger.kernel.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