From: David Littell <david.littell@prodeasystems.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Auth Packet TX Delay
Date: Thu, 17 Jan 2013 12:48:07 -0600 [thread overview]
Message-ID: <5F3A0E62E0444943B7E4DFE5C598B1154E52BD@prodeaserve.prodea.local> (raw)
Hi all,
I'm seeing a situation very similar to Robert's but instead using
hostapd on a 5 GHz channel. Clients attempting to authenticate cannot
unless I kill hostapd, ifconfig up, ifconfig down, and restart hostapd.
After that sequence clients can authenticate and appear to be working
normally.
Simply restarting hostapd without the ifconfig steps continues to not
work. However, following the ifconfig steps I can restart hostapd and
flip back and forth between 2.4 GHz and 5 GHz channels with no further
authentication failures.
What seems to be different is, unlike Robert's "periodic" problem, I've
never seen a 5 GHz channel work unless I go through the ifconfig steps.
If I change to a 2.4 GHz channel I have yet to see it fail to
authenticate clients.
I'm running hostapd 1.0 and compat-wireless-v3.6.8-1 ath9k.
Thanks,
Dave
This message is confidential to Prodea Systems, Inc unless otherwise indicated
or apparent from its nature. This message is directed to the intended recipient
only, who may be readily determined by the sender of this message and its
contents. If the reader of this message is not the intended recipient, or an
employee or agent responsible for delivering this message to the intended
recipient:(a)any dissemination or copying of this message is strictly
prohibited; and(b)immediately notify the sender by return message and destroy
any copies of this message in any form(electronic, paper or otherwise) that you
have.The delivery of this message and its information is neither intended to be
nor constitutes a disclosure or waiver of any trade secrets, intellectual
property, attorney work product, or attorney-client communications. The
authority of the individual sending this message to legally bind Prodea Systems
is neither apparent nor implied,and must be independently verified.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130117/484a00d3/attachment.htm
next reply other threads:[~2013-01-17 18:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 18:48 David Littell [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-20 18:45 [ath9k-devel] Auth Packet TX Delay Robert Shade
2013-01-15 22:06 ` Robert Shade
2013-01-16 23:09 ` Adrian Chadd
2013-01-17 1:00 ` Robert Shade
2013-01-17 3:12 ` Adrian Chadd
2013-02-06 2:51 ` Robert Shade
2013-02-06 3:08 ` Adrian Chadd
2013-02-06 12:53 ` Robert Shade
2013-02-06 22:58 ` Robert Shade
2013-02-07 5:06 ` Adrian Chadd
2013-02-07 16:25 ` David Littell
2013-02-07 16:25 ` David Littell
2013-02-07 19:43 ` Robert Shade
2013-02-07 21:40 ` Adrian Chadd
2013-02-08 18:48 ` Robert Shade
2013-02-09 7:39 ` Adrian Chadd
2013-03-24 18:55 ` Robert Shade
2013-03-24 21:52 ` Adrian Chadd
2013-03-24 22:40 ` Robert Shade
2013-03-24 22:58 ` Christian Lamparter
2013-03-25 0:03 ` Adrian Chadd
2013-03-25 2:23 ` Adrian Chadd
2013-03-25 16:12 ` Christian Lamparter
2013-03-25 16:45 ` Adrian Chadd
2013-03-26 12:21 ` Robert Shade
2013-03-26 13:23 ` Robert Shade
2013-03-26 16:28 ` Adrian Chadd
2013-03-26 16:29 ` Robert Shade
2013-03-26 17:13 ` Ben Greear
2013-03-26 17:13 ` Ben Greear
2013-03-26 17:16 ` Adrian Chadd
2013-03-26 17:16 ` Adrian Chadd
2013-03-26 17:27 ` Ben Greear
2013-03-26 17:27 ` Ben Greear
2013-03-26 17:33 ` Adrian Chadd
2013-03-26 17:33 ` Adrian Chadd
2013-03-26 17:45 ` Ben Greear
2013-03-26 17:45 ` Ben Greear
2013-03-27 0:55 ` Robert Shade
2013-03-27 0:55 ` Robert Shade
2013-03-27 3:11 ` Robert Shade
2013-03-27 3:11 ` Robert Shade
2013-03-27 16:33 ` Adrian Chadd
2013-03-27 16:33 ` Adrian Chadd
2013-03-26 17:14 ` Adrian Chadd
2013-03-26 14:13 ` Marco Fonseca
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=5F3A0E62E0444943B7E4DFE5C598B1154E52BD@prodeaserve.prodea.local \
--to=david.littell@prodeasystems.com \
--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.