From: Curby <curby@cur.by>
To: Markus Feldmann <feldmann_markus@gmx.de>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables NEW or SYN
Date: Thu, 13 May 2010 16:46:04 -0600 [thread overview]
Message-ID: <AANLkTikYXNQRQq4e-qX7IgMXT8UAOqR5ZTCgV7_Osof-@mail.gmail.com> (raw)
In-Reply-To: <hshruc$34i$1@dough.gmane.org>
On Thu, May 13, 2010 at 3:45 PM, Markus Feldmann <feldmann_markus@gmx.de> wrote:
> Thanks for your answer,
>
> i have an ESTABLISHED rule, look at line 127
Having a rule doesn't mean that it's doing what you want it to. =)
Since you have DROP policies, having EST/REL packets return to the
originating INPUT/FORWARD chain just drops them if nothing else
matches. Instead, try ACCEPT, as in:
iptables -A attacksinput -m state --state ESTABLISHED,RELATED -j ACCEPT
Can I get confirmation from Jan or someone else that a preferred and
more future-proof syntax is the following?
iptables -A attacksinput -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
--Mike
next prev parent reply other threads:[~2010-05-13 22:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 17:08 iptables NEW or SYN Markus Feldmann
2010-05-13 17:18 ` Jan Engelhardt
2010-05-13 17:42 ` Markus Feldmann
2010-05-13 18:00 ` Markus Feldmann
2010-05-13 18:09 ` Markus Feldmann
2010-05-13 20:09 ` Pascal Hambourg
2010-05-13 20:55 ` Markus Feldmann
2010-05-13 18:05 ` Markus Feldmann
2010-05-13 18:19 ` Curby
2010-05-13 18:45 ` Markus Feldmann
2010-05-13 19:23 ` Mistick Levi
2010-05-13 21:45 ` Markus Feldmann
2010-05-13 22:46 ` Curby [this message]
2010-05-14 0:06 ` Markus Feldmann
2010-05-14 0:23 ` Markus Feldmann
2010-05-14 2:19 ` Markus Feldmann
2010-05-14 6:41 ` Jan Engelhardt
2010-05-14 12:16 ` Markus Feldmann
2010-05-14 5:08 ` Mart Frauenlob
[not found] <hsgu5c$d8c$1@dough.gmane.org>
2010-05-13 15:21 ` ratheesh k
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=AANLkTikYXNQRQq4e-qX7IgMXT8UAOqR5ZTCgV7_Osof-@mail.gmail.com \
--to=curby@cur.by \
--cc=feldmann_markus@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).