From: Frank van Maarseveen <frankvm@frankvm.com>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
Kernel Netdev Mailing List <netdev@vger.kernel.org>
Subject: Re: 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE (2)
Date: Fri, 2 Jun 2006 16:02:12 +0200 [thread overview]
Message-ID: <20060602140212.GA7881@janus> (raw)
In-Reply-To: <20060602123559.GA7505@janus>
On Fri, Jun 02, 2006 at 02:35:59PM +0200, me wrote:
[...]
> This is a tcpdump done after rebooting "posio"
> to 2.6.13.2 showing how it should have looked:
[snip]
The 2.6.13.2 data is inconsistent. The bug appears to be present there at
well after closer examination. So there must be another factor involved
because I have at least one case logged where 2.6.13.2 did work (the
"sirkka" log in my previous mail). Applying your patch on 2.6.13.2
again removes the protocol is buggy messages (when doing a tcpdump)
but the problem of the 10 missing packets persists.
--
Frank
next prev parent reply other threads:[~2006-06-02 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060531094626.GA23156@janus>
2006-05-31 14:57 ` 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE Patrick McHardy
2006-05-31 16:06 ` Frank van Maarseveen
2006-05-31 16:36 ` Patrick McHardy
2006-05-31 17:29 ` Frank van Maarseveen
2006-05-31 17:46 ` Patrick McHardy
2006-05-31 18:20 ` Frank van Maarseveen
2006-06-01 9:11 ` Frank van Maarseveen
2006-06-01 17:34 ` Patrick McHardy
2006-06-02 12:35 ` Frank van Maarseveen
2006-06-02 14:02 ` Frank van Maarseveen [this message]
2006-06-02 14:16 ` 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE (2) Patrick McHardy
2006-06-02 14:39 ` Frank van Maarseveen
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=20060602140212.GA7881@janus \
--to=frankvm@frankvm.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).