From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Broken fragmentation
Date: Thu, 19 Jun 2008 23:25:34 +0200 [thread overview]
Message-ID: <1213910734.8967.117.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240806191409k7200ad53y654a7f8a117c8f14@mail.gmail.com> (sfid-20080619_230955_857500_99D66B2C)
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
> >> Fragments are in the air but the peer is not able to reassemble them.
> >> Something is wrong with the first fragment but I'm not sure yet.
> >
> > Hm, ok. got a packet capture? Maybe that was broken before, I remember
> > having problems with fragmentation but putting it down to the
> > known-to-be-completely-broken AP I was using.
>
> It is working the latest problem was caused by the driver, Yet i still
> don't understand the regression
> in the driver.
Hmm, ok.
> Would be nice if you can confirm it works also with another HW.
> Sending your patch out.
Thanks, I'll give it a try tomorrow with a better AP.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-06-19 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 9:20 Broken fragmentation Tomas Winkler
2008-06-19 9:56 ` Johannes Berg
2008-06-19 11:46 ` Tomas Winkler
2008-06-19 11:57 ` Tomas Winkler
2008-06-19 12:23 ` Johannes Berg
2008-06-19 13:08 ` Tomas Winkler
2008-06-19 13:24 ` Johannes Berg
2008-06-19 14:45 ` Tomas Winkler
2008-06-19 15:26 ` Johannes Berg
2008-06-19 18:13 ` Tomas Winkler
2008-06-19 18:16 ` Johannes Berg
2008-06-19 21:09 ` Tomas Winkler
2008-06-19 21:25 ` Johannes Berg [this message]
2008-06-25 9:50 ` Tomas Winkler
2008-06-25 10:02 ` Johannes Berg
2008-06-25 10:30 ` Tomas Winkler
2008-06-25 10:32 ` Johannes Berg
2008-06-25 10:35 ` Tomas Winkler
2008-06-25 10:42 ` Johannes Berg
2008-06-25 10:59 ` Tomas Winkler
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=1213910734.8967.117.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox