From: David Miller <davem@davemloft.net>
To: jukka.rissanen@linux.intel.com
Cc: netdev@vger.kernel.org, alex.aring@gmail.com
Subject: Re: [PATCH] 6lowpan: Uncompression of traffic class field was incorrect
Date: Thu, 14 Nov 2013 03:22:05 -0500 (EST) [thread overview]
Message-ID: <20131114.032205.1348397553819887559.davem@davemloft.net> (raw)
In-Reply-To: <1384333419-4087-1-git-send-email-jukka.rissanen@linux.intel.com>
From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Date: Wed, 13 Nov 2013 11:03:39 +0200
> If priority/traffic class field in IPv6 header is set (seen when
> using ssh), the uncompression sets the TC and Flow fields incorrectly.
>
> Example:
>
> This is IPv6 header of a sent packet. Note the priority/TC (=1) in
> the first byte.
>
> 00000000: 61 00 00 00 00 2c 06 40 fe 80 00 00 00 00 00 00
> 00000010: 02 02 72 ff fe c6 42 10 fe 80 00 00 00 00 00 00
> 00000020: 02 1e ab ff fe 4c 52 57
>
> This gets compressed like this in the sending side
>
> 00000000: 72 31 04 06 02 1e ab ff fe 4c 52 57 ec c2 00 16
> 00000010: aa 2d fe 92 86 4e be c6 ....
>
> In the receiving end, the packet gets uncompressed to this
> IPv6 header
>
> 00000000: 60 06 06 02 00 2a 1e 40 fe 80 00 00 00 00 00 00
> 00000010: 02 02 72 ff fe c6 42 10 fe 80 00 00 00 00 00 00
> 00000020: ab ff fe 4c 52 57 ec c2
>
> First four bytes are set incorrectly and we have also lost
> two bytes from destination address.
>
> The fix is to switch the case values in switch statement
> when checking the TC field.
>
> Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Applied, thanks.
prev parent reply other threads:[~2013-11-14 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 9:03 [PATCH] 6lowpan: Uncompression of traffic class field was incorrect Jukka Rissanen
2013-11-13 9:14 ` Alexander Aring
2013-11-14 8:22 ` David Miller [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=20131114.032205.1348397553819887559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--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).