All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Ritberg" <tim_rit@gmx.de>
To: netfilter@vger.kernel.org
Subject: Re: Incoming packet in wrong chain
Date: Sun, 08 Feb 2009 23:44:30 +0100	[thread overview]
Message-ID: <20090208224430.207240@gmx.net> (raw)
In-Reply-To: <498F4E63.8050603@inl.fr>

> For Netfilter connection tracking, a NEW TCP connection does not have to
> start with a SYN packet. If
> /proc/sys/net/netfilter/nf_conntrack_tcp_loose is set to 1 (default),
> Netfilter will try to pick up connection. By this mean, it is possible
> to recover a connection (in some fail-over case for example), but it
> introduces this looking-weird-at-first behaviour.
> 
> BR,
> - --
> Eric Leblond <eleblond@inl.fr>

because of that netfilter put it in INPUT-Chain?
and I wonder why it occurs randomly.
Should I switch  to nf_conntrack_tcp_loose 0?

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

  reply	other threads:[~2009-02-08 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 17:17 Incoming packet in wrong chain Tim Ritberg
2009-02-08 21:28 ` Eric Leblond
2009-02-08 22:44   ` Tim Ritberg [this message]
2009-02-09  7:19     ` Eric Leblond

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=20090208224430.207240@gmx.net \
    --to=tim_rit@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 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.