From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: Anatoly Muliarski <x86ever@gmail.com>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: Help me... please
Date: Sat, 02 Aug 2008 10:10:45 +0200 [thread overview]
Message-ID: <48941685.8080509@unipex.it> (raw)
In-Reply-To: <38db14850808012326g4e3e35b6yc6f1c8b5adf69120@mail.gmail.com>
Anatoly Muliarski wrote:
> Hi,
>
> You should remove -m state --state NEW statements because they track
> only START of connections.
>
Or you can accept the established and related _before_ to the other rules.
$IPTABLES -I INPUT 1 [FORWARD] -m state --state RELATED,ESTABLISHED -j
ACCEPT
However, can you send us the log that drop the traffic on the rule_39 ?
Michele
next prev parent reply other threads:[~2008-08-02 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 19:04 Help me... please linuxmc
2008-08-02 6:26 ` Anatoly Muliarski
2008-08-02 8:10 ` Michele Petrazzo - Unipex srl [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-02 8:57 linuxmc
2008-08-02 9:09 ` Michele Petrazzo - Unipex srl
2008-08-03 11:55 linuxmc
2008-08-03 12:12 linuxmc
2008-08-04 3:12 ` Anatoly Muliarski
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=48941685.8080509@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=netfilter@vger.kernel.org \
--cc=x86ever@gmail.com \
/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