On Thu, Sep 15, 2005 at 05:42:06PM -0400, Jeff Wolfe wrote:
>
> Note that if you're going to use the builtin AuthKrb5 module in Radiator
> 3.13, There are a couple obscure bugs with null passwords you might run
> into. I have some patches that I need to forward back to Hugh and the
> guys, I ju
UBC rolled out our WPA network this summer on 802.1x PEAP. Our next
milestone is fast-roaming support by caching the PMKs - not too sure if
we really have to wait for WPA2 or not
We expect 2 unique users this year... We are actively encouraging
users to move from the standard campus w
Wyman Miles wrote:
We're about to pilot an 802.1x project for one of the larger departments on
campus and I had a few questions for the universities who've gone before:
- is anyone using Kerberos as an authentication resource for your wireless
clients. Any pitfalls? Did you have to distribut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We're using 802.1x here at the University of Northern Iowa, but we're
just using PEAP/MSCHAPv2 against Microsoft's IAS against Active Directory.
The Windows native 802.1X client works, but it's a bit of a pain to
configure if the machine isn't in a do
et.
Can anyone verify this behavior?
-d
-Original Message-
From: Jon Moore [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 15, 2005 2:05 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] 802.1x rollout
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here at UPenn we use Kerberos for our backend authentication, using
EAP-TTLS-PAP. We also use Radiator as our backend RADIUS server.
The built-in Mac OS X supplicant (Internet Connect) works swimmingly.
We have been piloting third-party software
> - - is anyone using Active Directory as an authentication resource?
We are
> - - who's using native 802.1x supplicants versus who is
> distributing additional software? Of the latter group, any
> recommendations? (my personal leanings are Funk's 802.1x
> supplicant mated with the Open.com R
