From: Patrick McHardy <kaber@trash.net>
To: Nick Landry <nick.landry@gmail.com>
Cc: Christian Gorecki <christian.gorecki@post.rwth-aachen.de>,
netfilter-devel@lists.netfilter.org
Subject: Re: ipq_get_packet receives proper TCP and IP headers but the rest of payload is junk
Date: Fri, 06 Jul 2007 16:41:05 +0200 [thread overview]
Message-ID: <468E5481.3040203@trash.net> (raw)
In-Reply-To: <9010780e0707060712u586b0c77i31882b43c2028d2e@mail.gmail.com>
Nick Landry wrote:
> Thanks, I checked that but the issue is that I am sending the exact
> same GET request (Accept-Encoding is the same as well) for when the
> message passes through any of the machines. The read from ip_queue
> for one machine is headers + ascii which is what I'd expect. The
> other machine outputs headers + junk.
>
> Here's a hex dump for the machine that isn't working (payload length
> is 1500 bytes but I'll only print a small part):
>
> --> 45 00 05 78 02 37 40 00 42 06 18 5b 0a b3 00 0c
> --> 0a 2b 04 05 c5 3a 00 50 26 a2 08 34 a8 d5 7c f7
> --> 80 10 4f b0 de f3 00 00 08 0a e4 eb 14 02 d5 6e
> --> e4 1c 00 00 08 00 01 00 06 00 0f f7 b5 9b 00 00
> --> 00 00 00 00 00 00 00 00 30 00 00 00 00 00 00 00
> --> 45 00 00 30 bf 76 40 00 7c 06 d4 35 0a b1 2c 0f
> --> 0a b3 29 a9 13 4b 01 bd 29 7a 9e 75 00 00 00 00
> --> 70 02 40 00 fb 0b 00 00 02 04 05 b4 01 01 04 02
> --> 01 01 04 02 00 15 17 29 49 62 08 00 45 08 00 34
> --> 64 1b 40 00 40 06 be 0d 0a 2a 02 21 0a 2a 02 1f
> --> 80 03 bb 06 8c bc 41 58 79 bb 93 af 80 10 80 00
> --> 62 96 00 00 01 01 08 0a 00 2d 7d cc 19 d0 cd 3f
> --> b1 18 40 00 7e 00 40 00 00 00 00 00 82 00 16 00
> --> 38 18 04 00 7e 00 40 00 00 00 08 00 00 00 00 00
> --> 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> --> 00 00 00 00 00 00 00 00 b1 18 40 00 54 00 40 00
> --> 01 00 01 00 80 00 01 00 01 00 01 00 01 00 14 00
> --> 3b 03 05 00 7e 00 40 00 00 00 00 00 00 00 00 00
> --> 82 00 16 00 3e 00 07 00 b1 18 40 00 73 00 40 00
> --> 7e 00 40 00 00 00 00 00 00 00 00 00 82 00 16 00
> [....]
>
> And it just goes on like that. The NULLs are what leads me to believe
> that I'm getting back data that the kernel copied from the wrong part
> of memory (that and the output is different every time I run it, even
> though it's the same GET message).
Possibly related to ip_queue TSO handling bugs in old kernels. Are
you using TSO?
next prev parent reply other threads:[~2007-07-06 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9010780e0707060538r3c754988ibebe5fa7d0c11ff2@mail.gmail.com>
2007-07-06 12:39 ` ipq_get_packet receives proper TCP and IP headers but the rest of payload is junk Nick Landry
2007-07-06 13:00 ` Christian Gorecki
2007-07-06 14:12 ` Nick Landry
2007-07-06 14:41 ` Patrick McHardy [this message]
2007-07-06 15:38 ` Nick Landry
2007-07-06 17:48 ` Nick Landry
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=468E5481.3040203@trash.net \
--to=kaber@trash.net \
--cc=christian.gorecki@post.rwth-aachen.de \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nick.landry@gmail.com \
/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.