From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Marcel Laverdet <marcel@laverdet.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Problems getting NOTRACK to do anything at all
Date: Fri, 02 Oct 2009 15:49:43 +0200 [thread overview]
Message-ID: <4AC604F7.6060907@plouf.fr.eu.org> (raw)
In-Reply-To: <0d99e50d4f57cd74439c228559a6738c@localhost>
Hello,
Marcel Laverdet a écrit :
>
> For some reason I can't seem to get the NOTRACK iptables rule to do
> anything at all. Can anyone make sense of the following session which I
> think describes the problem better than words could. The session below was
> carried out on a reasonably busy server, and I didn't waste much time in
> between each command.
[...]
> fantasma marcel # iptables -t raw -A PREROUTING -i lo -j NOTRACK
I guess the raw/PREROUTING chain is too late for local traffic. Locally
generated packets are processed by conntrack in the NF_IP_LOCAL_OUT hook
unless the NOTRACK target was used in the raw/OUTPUT chain.
Try this instead :
iptables -t raw -A OUTPUT -o lo -j NOTRACK
next prev parent reply other threads:[~2009-10-02 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 12:40 Problems getting NOTRACK to do anything at all Marcel Laverdet
2009-10-02 13:49 ` Pascal Hambourg [this message]
2009-10-02 16:43 ` Marcel Laverdet
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=4AC604F7.6060907@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=marcel@laverdet.com \
--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