From: Benjamin Reed <breed@almaden.ibm.com>
To: jt@hpl.hp.com
Cc: Javier Achirica <achirica@ttd.net>, netdev@oss.sgi.com
Subject: Re: [PATCH] Dynamic airo.c patch for 2.6.10
Date: Wed, 02 Feb 2005 11:16:11 -0800 [thread overview]
Message-ID: <420126FB.3000007@almaden.ibm.com> (raw)
In-Reply-To: <20050202183525.GA13881@bougret.hpl.hp.com>
I'm wondering if it would be possible to change IW_ENCODE_TEMP to
IW_ENCODE_PERM. I realize that would not be backward compatible, but as
you point out, the default assumption is that the keys are volatile.
ben
Jean Tourrilhes wrote:
>Benjamin Reed wrote :
>
>
>>Here is a patch for the 2.6.10 aironet driver that
>>will enable dynamic wep keying without resetting the
>>MAC. It allows us to use xsupplicant with the driver.
>>
>>There are two lines of ugliness (the ones with the 0
>>&&) where I ignore the flag that says wether we are
>>setting a permanent or a temporary key since
>>xsupplicant doesn't use the IW_ENCODE_TEMP flag.
>>
>>
>
> The IW_ENCODE_TEMP flag only make sense for the Aironet
>driver, as for all other hardware the WEP keys are volatile. So, don't
>expect this flag to be widespread.
> I would suggest you send a nice little patch to the maintainer
>of xsupplicant (and wpa_supplicant as well) explaining the
>situation. Enabling this flag should not affect other drivers, and
>might actually be a good idea in general.
> Have fun...
>
> Jean
>
>
next prev parent reply other threads:[~2005-02-02 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 18:35 [PATCH] Dynamic airo.c patch for 2.6.10 Jean Tourrilhes
2005-02-02 19:16 ` Benjamin Reed [this message]
2005-02-02 19:22 ` Jean Tourrilhes
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 17:59 Benjamin Reed
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=420126FB.3000007@almaden.ibm.com \
--to=breed@almaden.ibm.com \
--cc=achirica@ttd.net \
--cc=jt@hpl.hp.com \
--cc=netdev@oss.sgi.com \
/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).