9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] wavelan driver, 802.1x supplicant
Date: Sun, 21 Aug 2005 03:12:47 +0200	[thread overview]
Message-ID: <200508210112.j7L1CmS17300@zamenhof.cs.utwente.nl> (raw)

I have been hacking the wavelan driver a bit to add 'fast key setting'
i.e. key setting without breaking the connection to the accesspoint.
this is needed by 802.1x when it updates wep keys 'on the fly'.
(for 802.1x supplicant see below)

I based the changes on a linux orinoco driver.
there were some differences between that one and ours.

most notably regarding use of registers Data0 and Data1.
using these more like in the linux driver seems to
avoids triggering the error message that was disabled in
our driver (because it seems we got it all the time).
(Information about proper usage of Data0/Data1 most welcome).

another difference is our use of 'include clear packets' vs.
their 'auth type open/shared-key'. Using the latter instead
of the former also seems to avoid triggering an error
msg from the card.

I maybe got carried away a bit when adding info to ifstats,
part of which is read afresh each time ifstats is read - 
which may be too much (esp. when most ifstats reading
is done by 'stats -8').

I think I did not break anything, but I wouldn't mind
having that confirmed by others.
To try, see:
	http://plan9.cs.utwente.nl/wlanfastkey/
which contains alternative wavelan.[ch] and
etherwavelan.c for /sys/src/9/pc .



I have a first rough cut of a 802.1x supplicant for ttls-pap,
which is the only thing I can test. If someone can
test other variants we might see how to add those.

it depends on tlshand patches I recently patch/create-ed,
and on the wlan driver fast key setting.

the code is not pretty, but seems to work. first rough cut.
constructive criticism is welcome, the README
gives some idea of what I hope to improve.

http://plan9.cs.utwente.nl/8021x.tgz


Enjoy,
Axel.


                 reply	other threads:[~2005-08-21  1:12 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=200508210112.j7L1CmS17300@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).