From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Subject: Re: 802.15.4 6LoWPAN fragmentation is broken
Date: Wed, 14 Jan 2015 15:16:01 +0100 [thread overview]
Message-ID: <20150114141600.GB19961@omega> (raw)
In-Reply-To: <20150113112016.GA14472@omega>
Hi,
On Tue, Jan 13, 2015 at 12:20:16PM +0100, Alexander Aring wrote:
> Hi,
>
> I notice some issue with fragmentation code.
>
> There is some magic number like:
>
> ping6 2001::1 -s 2145
>
> with a payload of 2144 it works. It seems that all payloads above
> 2144 are broken. I will try to bisect this issue. I see this issue also
> in net-next. I suppose it's something with the inet_frag API.
>
>
> ... so don't worry I already working on it.
>
Status update to this:
I detected that systemd changed the default net scheduler to fq_codel. [0]
With fq_codel seems that 6LoWPAN fragmentation is broken.
For now: please don't use this scheduler. I will try to find out why we have
fragmentation issues with fq_codel.
- Alex
[0] http://cgit.freedesktop.org/systemd/systemd/commit/?id=e6c253e363dee77ef7e5c5f44c4ca55cded3fd47
prev parent reply other threads:[~2015-01-14 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 11:20 802.15.4 6LoWPAN fragmentation is broken Alexander Aring
2015-01-14 14:16 ` Alexander Aring [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=20150114141600.GB19961@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@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