linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Platte <jplatte@naasa.net>
To: linux-wireless@vger.kernel.org
Subject: rt61pci and group re-keying
Date: Mon, 08 Oct 2012 19:49:28 +0200	[thread overview]
Message-ID: <50731228.6040507@naasa.net> (raw)

Hi list,

I'm using an Intel based computer with a network card supported by the 
rt61pci driver. This computer has a quite strange problem, sometimes it 
cannot be connected from other computers in the same network, sometimes 
it can. Today I have spent some time to debug this and it looks like the 
problem is caused by the group rekeying (rt61pci_config_shared_key). I'm 
using WPA2 with TKIP group key.

Here the problem. After first association everything works and it still 
works after the first re-keying. After the second one the computer no 
longer responds to pings (arp "who has" request gets no answer). Then, 
after the next re-keying it works again (and so on). So basically only 
the first, third, fifth and so on re-keing works. After adding some 
debug information to the driver I think that the driver is doing the 
right thing. In total two keys are marked as active and before the third 
re-keying the oldest one is deleted via DISABLE_KEY.

I solved the problem by setting only the new key as valid by changing
         if (crypto->cmd == SET_KEY)
                 reg |= mask;

to

         if (crypto->cmd == SET_KEY)
                 reg = mask;


However, the hardware seems to be able to support up to four keys. Do 
you have any idea why the card behaves wrongly? Kernel is 2.6.36.2, but 
according to git there are no important changes on recent kernels for 
this driver.

Best regards,
Joerg

                 reply	other threads:[~2012-10-08 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50731228.6040507@naasa.net \
    --to=jplatte@naasa.net \
    --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).