From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Steuerwald <salsasepp@googlemail.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org
Subject: Re: Fwd: p54: testing AP mode: cannot switch to master mode
Date: Fri, 21 Nov 2008 10:36:05 +0100 [thread overview]
Message-ID: <1227260165.3766.60.camel@johannes.berg> (raw)
In-Reply-To: <f76a32050811210037x5958de39g53b174b2d0dfd41b@mail.gmail.com> (sfid-20081121_093709_047280_C86566C8)
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
On Fri, 2008-11-21 at 09:37 +0100, Stefan Steuerwald wrote:
> indeed I overlooked the AID bit in the relevant traffic sequences.
> Knowing now what to look for, I can follow what is going on and find
> it ok - except for the huge delay in between http request and reply.
> Typically, the http request is sent, the iPod goes to sleep, and
> several seconds pass (with numerous beacons without any AID bit set),
> before we see one or two "traffic for you" beacons, then the iPod
> wakes up and gets the reply. Most of the time my app already
> timeouted.
>
> I have checked that my app indeed completes its TCP reply in almost no
> time. Mysteriously, the data takes several seconds from boost::asio
> write completion until it appears on the air. That's the problem.
>
> I will go back to square one and the fact that I see different
> behaviour in the iPod and my other clients. I will work out the
> differences. Will be back in case I come up with more wireless
> questions.
Well, there could a buffering error in mac80211/p54 too. You could
enable verbose power save mode debugging (mac80211 debug kconfig,
normally not recommended to turn on); that will then print to the kernel
log whenever data for the station is being buffered and the AID bit will
be set. Since multiple seconds pass, you should be able to correlate
whether or not the AID bit is sent in the beacon right away after
mac80211 requests that, or not.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-21 9:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f76a32050811190306s6a86f46dwc245200069ff8a82@mail.gmail.com>
2008-11-19 11:16 ` Fwd: p54: testing AP mode: cannot switch to master mode Stefan Steuerwald
2008-11-19 11:56 ` Johannes Berg
2008-11-19 15:37 ` Stefan Steuerwald
2008-11-19 15:41 ` Johannes Berg
2008-11-19 16:23 ` Stefan Steuerwald
2008-11-19 20:23 ` Johannes Berg
2008-11-20 8:50 ` Stefan Steuerwald
2008-11-20 13:44 ` Stefan Steuerwald
2008-11-20 14:37 ` Holger Schurig
2008-11-20 17:59 ` Johannes Berg
2008-11-20 19:21 ` Stefan Steuerwald
2008-11-20 19:29 ` Johannes Berg
2008-11-20 19:58 ` Johannes Berg
2008-11-21 7:38 ` Holger Schurig
2008-11-21 8:37 ` Stefan Steuerwald
2008-11-21 9:36 ` Johannes Berg [this message]
2008-11-23 14:32 ` Johannes Berg
2008-11-24 13:11 ` Stefan Steuerwald
2008-11-20 14:49 ` Holger Schurig
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=1227260165.3766.60.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=salsasepp@googlemail.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