From: Patrick McHardy <kaber@trash.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: netdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] SNAT sometimes allows packets to pass through unchanged
Date: Mon, 16 Feb 2009 11:43:27 +0100 [thread overview]
Message-ID: <4999434F.1050101@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0902121008050.2388-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 12 Feb 2009, Patrick McHardy wrote:
>
>> If the connection has already timed out (from conntracks perspective),
>> it has lost its state. Unless connection pickup is enabled, the packet
>> will be marked as INVALID because it doesn't belong to a connection.
>> You can control dropping of these packets yourself by adding the
>> appropriate "-m state --state INVALID" rules.
>
> I tried adding a rule to log these unaccounted-for packets. Nothing
> showed up, even when I could see the packets being sent.
Where (table/chain/position) did you add this rule?
>> That said, there were
>> some bugs in the past few releases that caused some bad interaction
>> between TCP and TCP conntrack (not sure anymore which one of both was
>> to blame). Its possible that this is the root cause for this, so
>> you might want to consider a kernel update.
>
> It does sound like the result of a bug. Do you have any pointers to
> patches or locations to check in the source?
Sorry, there were quite a few patches and I don't remember which
ones exactly are related.
next prev parent reply other threads:[~2009-02-16 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 17:37 [BUG] SNAT sometimes allows packets to pass through unchanged Alan Stern
2009-02-12 5:18 ` Patrick McHardy
2009-02-12 15:11 ` Alan Stern
2009-02-16 10:43 ` Patrick McHardy [this message]
2009-02-16 16:19 ` Alan Stern
2009-02-16 16:25 ` Patrick McHardy
2009-02-16 16:41 ` Alan Stern
2009-02-18 16:49 ` Alan Stern
2009-02-18 16:58 ` Patrick McHardy
2009-02-18 17:41 ` Alan Stern
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=4999434F.1050101@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.