All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mats Johannesson <spamcan1@abrasax.se>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k constantly drops network connection
Date: Thu, 18 Sep 2008 10:36:28 +0200	[thread overview]
Message-ID: <20080918103628.5a6ab12c@loke.fish.not> (raw)
In-Reply-To: <20080918044618.0cd64cd9@loke.fish.not>

On Thu, 18 Sep 2008 04:46:18 +0200 Mats Johannesson wrote:
> On Wed, 17 Sep 2008 12:10:03 -0700 Luis R. Rodriguez wrote:
> > On Wed, Sep 17, 2008 at 03:05:59AM -0700, Partha Bagchi wrote:
> [...]
> > > 03:42:27 EDT 2008 i686 i686 i386 GNU/Linux
> > 
> > Please try appling the patch titled:
> > 
> > "[PATCH] ath9k: connectivity is lost after Group rekeying is done"
> > 
> > which was posted on linux-wireless. If that fixes your issue I can
> 
> A question Luis. Looking at the code (and not knowing _anything_ about
> wireless internals):
> 
> -		if (sc->sc_keytype == ATH9K_CIPHER_WEP)
> +		if (tx_info->control.hw_key->alg == ALG_WEP)
>  			txctl->keytype = ATH9K_KEY_TYPE_WEP;
> -		else if (sc->sc_keytype == ATH9K_CIPHER_TKIP)
> +		else if (tx_info->control.hw_key->alg == ALG_TKIP)
>  			txctl->keytype = ATH9K_KEY_TYPE_TKIP;
> -		else if (sc->sc_keytype == ATH9K_CIPHER_AES_CCM)
> +		else if (tx_info->control.hw_key->alg == ALG_CCMP)
>  			txctl->keytype = ATH9K_KEY_TYPE_AES;
> 
> I'm confused regarding the AES cypher. My AP is set through its
> interface as:
> 
> Security Mode: WPA-Personal
> WPA Mode: WPA2 Only
> Cipher Type: AES
> Group Key Update Interval: 2461 seconds (~41 minutes)
> Pre-Shared Key: Loooong long key.
> 
> But the output from "iwlist scan" tells another story:
> 
>                     Encryption key:on
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : TKIP
>                         Pairwise Ciphers (1) : TKIP
>                         Authentication Suites (1) : PSK
> 
> So someones lying... Does this effect ath9k?
> 
> I'll compile another kernel and try to get rid of TKIP stuff
> completely to test this out. At the moment the environment looks like
> this:
> 
> grep -i tkip my-.config
> grep -i michael my-.config
> # CONFIG_CRYPTO_MICHAEL_MIC is not set
> grep -i ecb my-.config
> CONFIG_CRYPTO_ECB=m
> grep -i aes my-.config
> CONFIG_CRYPTO_AES=m
> CONFIG_CRYPTO_AES_X86_64=m
> 
> loke at sleipner:~$ lsmod|grep -i ecb
> ecb                     1344  2
> crypto_blkcipher        8964  1 ecb
> crypto_algapi           6336  6
> aes_x86_64,aes_generic,arc4,ecb,crypto_blkcipher,cryptomgr
> 
> loke at sleipner:~$ lsmod|grep -i aes
> aes_x86_64              6784  3
> aes_generic            25576  1 aes_x86_64
> crypto_algapi           6336  6
> aes_x86_64,aes_generic,arc4,ecb,crypto_blkcipher,cryptomgr
> 
> Perhaps I'll break ath9k if the kernel lets me compile without an ecb
> module...

Well, it didn't let me deselect ecb since that is selected by MAC80211
(as is arc4).

Anyhow, writing now to share the good news that the patch you refer to:
[PATCH] ath9k: connectivity is lost after Group rekeying is done
(Click on [Download message RAW] at
http://marc.info/?l=linux-wireless&m=122163541519736&w=2 to get a clean
copy) completely fixes the regression between -rc5 and -rc6 I reported
in:

[ath9k-devel] 2.6.27-rc6 (and forwartd to -rc6-git3) dies silently.
https://lists.ath9k.org/pipermail/ath9k-devel/2008-September/000263.html

Patching -rc6-git3 I've now run 4 hours without a connection drop.
Strangely enough it also allowed me to again make the connection
'sticky' over a reboot (Wicd Manager).

This patch is a must have for 2.6.27 no matter what merging policy is
in effect.

Mvh
Mats Johannesson

  reply	other threads:[~2008-09-18  8:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 10:05 [ath9k-devel] ath9k constantly drops network connection Partha Bagchi
2008-09-17 19:10 ` Luis R. Rodriguez
2008-09-17 23:08   ` Partha Bagchi
2008-09-17 23:20     ` Luis R. Rodriguez
2008-09-18 10:04       ` Partha Bagchi
2008-09-18 10:09         ` Luis R. Rodriguez
2008-09-18 10:45           ` Partha Bagchi
2008-09-18 11:02             ` Mats Johannesson
2008-09-18 23:01               ` Partha Bagchi
2008-09-19  9:59                 ` Partha Bagchi
2008-09-19 17:43                   ` Luis R. Rodriguez
2008-09-19 22:30                     ` Partha Bagchi
2008-09-19 23:49                       ` Luis R. Rodriguez
2008-09-20 12:36                         ` Partha Bagchi
2008-09-20 13:07                           ` Partha Bagchi
2008-09-20 19:57                             ` Luis R. Rodriguez
2008-09-20 20:31                               ` Partha Bagchi
2008-09-20 20:54                                 ` Luis R. Rodriguez
2008-09-20 21:19                                   ` Partha Bagchi
2008-09-20 22:54                                     ` Luis R. Rodriguez
2008-09-20 23:38                                       ` Partha Bagchi
2008-09-20 23:48                                         ` Luis R. Rodriguez
2008-09-20 23:56                                           ` Partha Bagchi
2008-09-22  6:52                                             ` Luis R. Rodriguez
2008-09-18  2:46   ` Mats Johannesson
2008-09-18  8:36     ` Mats Johannesson [this message]
2008-09-18  8:46       ` Luis R. Rodriguez
2008-09-18  8:46         ` Luis R. Rodriguez
2008-09-18  9:00         ` Steven Noonan
2008-09-18  9:00           ` Steven Noonan

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=20080918103628.5a6ab12c@loke.fish.not \
    --to=spamcan1@abrasax.se \
    --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.