All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Laverdet <marcel@laverdet.com>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: Problems getting NOTRACK to do anything at all
Date: Fri, 02 Oct 2009 11:43:55 -0500	[thread overview]
Message-ID: <4d3950064f1ab4c86937b59d8a1a3a99@localhost> (raw)
In-Reply-To: <4AC604F7.6060907@plouf.fr.eu.org>



Yes, that was it! This was also the hint I needed to get some more complex
rules setup and now everything is working just the way I want.

Merci!

On Fri, 02 Oct 2009 15:49:43 +0200, Pascal Hambourg
<pascal.mail@plouf.fr.eu.org> wrote:
> 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

      reply	other threads:[~2009-10-02 16:43 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
2009-10-02 16:43   ` Marcel Laverdet [this message]

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=4d3950064f1ab4c86937b59d8a1a3a99@localhost \
    --to=marcel@laverdet.com \
    --cc=netfilter@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.