All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tamas Selmeci <tselmeci@dension.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] WPA/WPA2 problem with ath9k
Date: Fri, 13 Feb 2009 11:51:05 +0100	[thread overview]
Message-ID: <49955099.3000309@dension.com> (raw)

Hello all!

On our hotspot apart from Samsung mobiles everything is ok until there's 
no security switched on.

As soon as WPA/WPA2 (or any combination of them including TKIP/CCMP) is 
switched on, connecting to the AP becomes extremely slow and fails 
several times. Once it gets connected seems to work perfectly, but I 
can't beleive that it should be that slow.

Environment:
- linux-2.6.27-rc6;
- ath9k-compat: 2009-01-25 and 2009-02-11;
- AR5416
- hostapd-0.6.7

hostapd.conf is as follows:

interface=wlan0
driver=nl80211
hw_mode=g
country_code=DE
max_num_sta=32
# supported_rates=10 20 55 110 60 90 120 180 240 360 480 540
# ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40]
logger_syslog=1
logger_syslog_level=0
logger_stdout=-1
logger_stdout_level=0
debug=1
ctrl_interface_group=0
macaddr_acl=0
auth_algs=1
dump_file=/tmp/hostapd.dump
ssid=norbolataska
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP CCMP
rsn_pairwise=TKIP CCMP
ap_max_inactivity=120
wpa_psk=af8f7d04a3331126ee9fad0cf2dbba54728389d93d83ca1549dfda2727249890
channel=8

Do you have any idea what can be wrong? I heard that AR5416 is a rather 
buggy card, many of the bugs have been fixed in AR9160, but that's also 
problematic according to my experiences. Adding "ieee80211n=1" didn't 
solve the problem.

Regards,
-- 
Tamas Selmeci

             reply	other threads:[~2009-02-13 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 10:51 Tamas Selmeci [this message]
2009-02-13 21:46 ` [ath9k-devel] WPA/WPA2 problem with ath9k Luis R. Rodriguez
2009-02-16  8:33   ` Tamas Selmeci

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=49955099.3000309@dension.com \
    --to=tselmeci@dension.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.