From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9380 frequent disconnect and stucks in AP mode.
Date: Tue, 07 May 2013 14:17:00 +0200 [thread overview]
Message-ID: <5188F0BC.6080002@openwrt.org> (raw)
In-Reply-To: <20130507120609.3E8543116FC@venema.h4ckr.net>
On 2013-05-07 2:03 PM, Bhavesh Kamani wrote:
>
> Hi Ben,
>
> I tried compat-drivers-3.9-rc4-2-su, then also same problem I faced.
> I also tried compat-wireless-2.6.39-1 and compat-wireless-3.6.8-1, but
> facing the same issue.
>
> In a day more than one clients are facing the same issue.
>
> In the locked state, ping from client to AP not working and tcpdump on AP
> shows the echo response sent on wlan interface. Only few clients are facing
> this issue frequently, but those clients don't have identical WiFi hardware.
>
> Is it possible for hardware/firmware to drop the tx packets for particular
> client? For me look like only data packets are getting dropped.
> My environment is noisy, will it affect this situation?
You should also upgrade hostapd to something recent. It's relevant for
AP mode stability as well.
- Felix
next prev parent reply other threads:[~2013-05-07 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 14:03 [ath9k-devel] AR9380 frequent disconnect and stucks in AP mode Bhavesh Kamani
2013-05-06 14:23 ` Ben Greear
2013-05-07 12:03 ` Bhavesh Kamani
2013-05-07 12:17 ` Felix Fietkau [this message]
2013-05-08 12:44 ` Bhavesh Kamani
-- strict thread matches above, loose matches on Subject: below --
2013-05-08 13:20 Bhavesh Kamani
[not found] <201305081322.r48DMkDt011184@ns3.lanforge.com>
2013-05-08 16:02 ` Ben Greear
2013-05-10 9:20 ` bhavesh.kamani at elitecore.com
2013-05-10 9:20 ` bhavesh.kamani at elitecore.com
2013-05-10 14:37 ` Ben Greear
2013-05-14 7:17 ` Bhavesh Kamani
2013-05-14 7:21 Bhavesh Kamani
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=5188F0BC.6080002@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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 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.