The only authentication mechanism that makes sense for wireless is to
use 802.1x, which implies a Radius server. The AP talks to the Radius
server, which in turn authenticates against your database (can be local,
LDAP, SQL, whatever). On the client side you will need an 802.1x
"supplicant" (client). While Windows XP ships with one, it is not very
useable in NetWare environments as you can't authenticate to the
wireless network *prior* to logging into eDirectory. To to that, you
need a third-party supplicant such as Funk's Odyssey or the Aegis client.
On the server side, you will not be able to use the BM Radius server. It
does not have the necessary access methods such as EAP-TTLS, PEAP, etc
necessary for wireless authentication, and never will. You will have to
go with either the open source freeRADIUS product, or a commercial
Radius server such as Radiator, Stell Belted Radius, etc.
--
Jim
NSC SYsop
>I'm planning on installing an Aruba 2400 WLAN switch in our Netware 6
>network, for purposes of providing wireless network connectivity.
RADIUS. Specifically FreeRADIUS. See the TUT 145 session from BrainShare 2005,
titled "Configuring eDirectory for 802.11 Wireless Authentication".
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
Well, it's certainly technically possible, yes, just much less common
than Radius. I've only ever seen such functionality in a wireless
"switch" (is that what the Aruba is?) and not an AP, but I guess
anything is possible.
--
Jim
NSC SYsop