From: Jouni Malinen <jouni@qca.qualcomm.com>
To: Haohui Liao <liaohaohui@gmail.com>
Cc: <linux-wireless@vger.kernel.org>, <ath9k-devel@lists.ath9k.org>
Subject: Re: [ath9k-devel] Wireless stalled after a few minutes with Linux Kernel 3.1
Date: Mon, 5 Dec 2011 12:37:51 +0200 [thread overview]
Message-ID: <20111205103751.GA3775@jouni.qca.qualcomm.com> (raw)
In-Reply-To: <CAHW5WCJhwGSM74nN5ivoEgP98y_hbbOB8yDO9+2ahhy2B4H7yw@mail.gmail.com>
On Sat, Dec 03, 2011 at 10:55:40PM +0800, Haohui Liao wrote:
> Dear Linux Wifi developers,
>
> Regarding https://bugs.archlinux.org/task/27406
>
> > The following is a portion of my wpa_supplicant.conf
> >
> > ssid="LINUX-LINK"
> > proto=WPA2
> > key_mgmt=WPA-PSK
> > pairwise=TKIP
> > group=TKIP
That's pretty strange configuration.. Do you have any particular reason
for using TKIP as the pairwise cipher with WPA2? CCMP would be much more
likely configuration for WPA2 in general..
> Just wondering if I am the only one still doing the following from command line
> to connect to wifi?
I'm sure you are not the only one.. And in this particular case, I don't
see how that would make a difference.
> wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
> iwconfig wlan0 power off
> dhcpd wlan0
>
> If I do that, I will get wifi stall on wpa_supplicant when there is a
> rekeying with the Linux 3.1.x kernel. It does not happen to Linux
> 3.0.x. I have been searching on Internet around with no indicator.
> Just trying to ask if I did anything wrong? or everyone just uses
> NetworkManager?
Would you be able to provide some more details on what exactly you mean
with "wifi stall"? Are you sure this is related to rekeying?
May I ask why you have configured the station to force PTK rekeying
every 10 minutes? While TKIP is not really the most secure design out
there, the proper way of addressing this would be to use CCMP instead of
frequent rekeying with TKIP..
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2011-12-05 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 14:20 Wireless stalled after a few minutes with Linux Kernel 3.1 Haohui Liao
2011-11-19 17:28 ` Arend van Spriel
[not found] ` <CAHW5WCLUefvgvRkgz7Nr+Rwu6_96t7EVVB33U0ED5g9a0cHFXw@mail.gmail.com>
2011-11-25 13:26 ` Arend van Spriel
2011-11-27 8:16 ` Haohui Liao
2011-12-03 14:55 ` Haohui Liao
2011-12-04 2:51 ` Adrian Chadd
2011-12-05 10:37 ` Jouni Malinen [this message]
2011-12-09 13:07 ` [ath9k-devel] " Haohui Liao
2011-12-09 13:41 ` Jouni Malinen
[not found] ` <CAHW5WC+6f1137kP3mvsC4umnRD2j04==dBJEFZyjrciHwYhp+Q@mail.gmail.com>
2011-12-27 12:27 ` Haohui Liao
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=20111205103751.GA3775@jouni.qca.qualcomm.com \
--to=jouni@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=liaohaohui@gmail.com \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).