From: Jean Tourrilhes <jt@hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Benjamin Reed <breed@zuzulu.com>
Cc: Jouni Malinen <jkmaline@cc.hut.fi>, chessing@users.sourceforge.net
Subject: Re: [PATCH] dynamic wep keys for airo.c
Date: Tue, 3 May 2005 11:33:35 -0700 [thread overview]
Message-ID: <20050503183335.GA19691@bougret.hpl.hp.com> (raw)
Benjamin Reed wrote :
>
> I'm resubmitting a patch for the 2.6.11.8 aironet driver (airo.c) that will
> enable dynamic wep keying without disabling the MAC. It allows
> us to use xsupplicant with the driver.
>
> Aironet provides the ability to set WEP keys permanently or
> temporarily. There is a special IW_ENCODE_TEMP flag for selecting
> which type of key you are setting. However, apart from iwconfig,
> nobody seems to use this flag. When a permanent WEP key is set,
> the MAC must be disabled. I have added a module parameter to skip
> disabling the MAC even if a permanent WEP key is set. Using this
> flag allows xsupplicant to work without modification.
Hmm... I don't know why you are so afraid of submitting a
patch to xsupplicant (and wpa_supplicant). Having xsupplicant *always*
setting IW_ENCODE_TEMP would be worthwhile. Have you even try to
submit a patch to the author of xsupplicant ?
There was other driver having issues with with not reseting
the MAC while changing the WEP key. For example, some Lucent firmware
may lock up if you set WEP without fully reseting the MAC. So, having
IW_ENCODE_TEMP in xsupplicant would mean that the driver could support
802.1x properly if the firmware is sane and remain conservative while
setting static WEP keys, i.e. the best of both words. Driver that are
sane (moder hardware) can just ignore IW_ENCODE_TEMP.
With respect to airo, I think it would be nice if xsupplicant
did not pollute the WEP EEprom, so that next time you roam to a static
WEP AP, you can resuse the EEprom keys.
In summary, I believe that a correct solution is not so
difficult to implement (just a 2 line patch for xsupplicant and
wpa_supplicant), therefore I don't beleive we should go with
workarounds.
Have fun...
Jean
next reply other threads:[~2005-05-03 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 18:33 Jean Tourrilhes [this message]
[not found] ` <4277C8CA.5070503@utah.edu>
2005-05-03 19:59 ` Jean Tourrilhes
2005-05-03 22:34 ` breed
2005-05-03 23:13 ` Jean Tourrilhes
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 15:26 Benjamin Reed
2005-05-06 8:04 ` Domen Puncer
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=20050503183335.GA19691@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=breed@zuzulu.com \
--cc=chessing@users.sourceforge.net \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®