From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Luis Rodriguez <mcgrof@gmail.com>
Subject: ath5k AP issues
Date: Thu, 29 Oct 2009 13:30:24 +0100 [thread overview]
Message-ID: <200910291330.26172.mb@bu3sch.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Attached is a wireshark log. Let me explain what you see in there:
I have an ath5k AP and the powersaving n810 device as STA.
What I try to do is ping the n810. You can see that at the start of the log.
Packet #31 is a ping to the n810. #42, too. and so on...
You see that the n810 does not reply. (not even with an 802.11 ack)
I guess the n810 is in PS at that time.
Also note that the TIM sent by the AP is empty.
What I did at #135 is _simultaneously_ ping from the n810 to the ath5k.
At that point suddenly both pings running on both ends start to succeed.
This is with a vanilla 2.6.31.5 kernel, but I can also reproduce this with
compat-wireless and compat-wireless-stable.
--
Greetings, Michael.
[-- Attachment #2: capture --]
[-- Type: application/octet-stream, Size: 41364 bytes --]
next reply other threads:[~2009-10-29 12:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 12:30 Michael Buesch [this message]
2009-10-29 13:06 ` ath5k AP issues Michael Buesch
2009-10-29 13:31 ` Michael Buesch
2009-10-31 20:21 ` Bob Copeland
2009-11-01 6:53 ` Nick Kossifidis
2009-11-01 6:56 ` Nick Kossifidis
2009-11-01 13:16 ` Bob Copeland
2009-11-01 13:41 ` Nick Kossifidis
2009-11-01 14:44 ` [ath9k-devel] " Bob Copeland
2009-11-01 14:44 ` Bob Copeland
2009-11-02 19:43 ` [ath9k-devel] " Bob Copeland
2009-11-02 19:43 ` Bob Copeland
2009-11-02 21:36 ` [ath9k-devel] " Nick Kossifidis
2009-11-02 21:36 ` Nick Kossifidis
2009-11-03 19:27 ` [ath9k-devel] " Bob Copeland
2009-11-03 19:27 ` Bob Copeland
2009-11-03 20:44 ` [ath9k-devel] " Nick Kossifidis
2009-11-03 20:44 ` Nick Kossifidis
2009-11-01 10:34 ` Michael Buesch
2009-10-29 13:29 ` Johannes Berg
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=200910291330.26172.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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.