linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: hce <webmail.hce@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: Patch for linux wireless extension
Date: Fri, 07 Mar 2008 07:11:41 -0500	[thread overview]
Message-ID: <1204891901.20146.7.camel@localhost.localdomain> (raw)
In-Reply-To: <95455e980803061900g5890a860n5c000a974cdf30b0@mail.gmail.com>

On Fri, 2008-03-07 at 14:00 +1100, hce wrote:
> On Fri, Mar 7, 2008 at 1:00 AM, Dan Williams <dcbw@redhat.com> wrote:
> >
> > On Thu, 2008-03-06 at 21:37 +1100, hce wrote:
> >  > On 3/5/08, Dan Williams <dcbw@redhat.com> wrote:
> >  > > On Tue, 2008-03-04 at 11:26 +0100, Johannes Berg wrote:
> >  > >  > Jim,
> >  > >  >
> >  > >  > > I am running a wifi device on kernel 2.6.11 and wireless extension
> >  > >  > > version 17 for an ARM processor, it works fine with an open AP and
> >  > >  > > wpa_supplicant 0.5.8.
> >  > >  >
> >  > >  > That's ancient.
> >  > >  >
> >  > >  > > Now I would like to support WEP and WPA. I know
> >  > >  > > the best is to upgrade to latest kernel, but I am not in the position
> >  > >  > > to do it as various reasons.
> >  > >  >
> >  > >  > Upgrade anyway.
> >  > >  >
> >  > >  > > An alternative as people suggested is to
> >  > >  > > do a wireless extension patch which supports WEP and WPA on kernel
> >  > >  > > 2.6.11. Any advice if it is feasible and where can I find the wireless
> >  > >  > > extension patch for WEP and WPA on kernel 2.6.11 please?
> >  > >  >
> >  > >  > Hahaha. We'll you'll have to *make* that patch and invest a
> >  > >  > *significant* amount of time into that.
> >  > >
> >  > >
> >  > > Yeah; it's not just the defines and whatnot in wireless.h; you probably
> >  > >  also want to update wireless-tools too, then you have to update your
> >  > >  driver as well.  It's not hugely complex, but it's going to be a lot of
> >  > >  boring work :)
> >  > >
> >  > >
> >  > >  Dan
> >  >
> >  > I've just upgrade wireless extension version 18 which supports WPA (Is
> >  > it for WEP as well?), with replaced two files of version 18 wireless.h
> >  > and wireless.c in the kernel 2.6.11. Please correct me if I missed
> >  > other source files in the kernel.
> >  >
> >  > The wireless-tools we are using come from different sources, the
> >  > iwconfig was from busybox 1.3 and wpa_supplicant 0.5.8 was compiled to
> >  > our firmware. The initial test for WEP set up was not good, but I was
> >  > told, the wireless extension vresion 18 only supports WPA not WEP,
> >  > please advice.
> >
> >  Incorrect.  WE-18 _added_ support for WPA ioctls but did not remove
> >  support for WEP.  You'll just have to debug stuff and find out what's
> >  going wrong.
> 
> Thanks Dan.
> 
> There was an error of "ioctl[SIOCSIWENCODEEXT]: Input/output error". I
> looked at wireless.h and wireless.c of WE18, that the
> "SIOCSIWENCODEEXT" is defined and it also defines following in the
> static const struct iw_ioctl_description standard_ioctl[]
> 
> [SIOCSIWENCODEEXT - SIOCIWFIRST] = {
>         .header_type    = IW_HEADER_TYPE_POINT,
>         .token_size = 1,
>         .min_tokens = sizeof(struct iw_encode_ext),
>         .max_tokens = sizeof(struct iw_encode_ext) +
>                 IW_ENCODING_TOKEN_MAX,
>     },
> 
> What could I be missing for that ioctl[SIOCSIWENCODEEXT] in the kernel?

Well, if you want to support WPA you _also_ have to update your driver
with the ENCODEEXT and AUTH calls, and have your driver deliver WPA and
RSN IEs in the scan results with the GENIE tag.

There might also be something wrong with the backport, the IO error
reported looks odd.  I'm not an expert on the implementation of WEXT in
wireless.c though and I'm unsure what the exact path is that the ioctl
takes before it gets to the driver :(

Dan



      reply	other threads:[~2008-03-07 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  3:01 Patch for linux wireless extension hce
2008-03-04 10:26 ` Johannes Berg
2008-03-04 13:58   ` Dan Williams
2008-03-06 10:37     ` hce
2008-03-06 14:00       ` Dan Williams
2008-03-07  3:00         ` hce
2008-03-07 12:11           ` Dan Williams [this message]

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=1204891901.20146.7.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=webmail.hce@gmail.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).