You and Julian are, of course, right about both Radiator and SBR. I
was thinking about the problem from a different angle, where the PEAP/
TTLS session was terminating on a foreign system (as is the case with
roaming, commercial service providers or a distributed education
environment).
Th
If, in the RADIUS Access-Accept, a User-Name attribute is included,
then, according to the spec, the NAS *must* use that value in any
accounting records. So, if you can get your RADIUS server to return
the User-Name used in the inner exchange as the User-Name in the
final Access-Accept, th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 15:34 -0700 06/01/2006, David Morton wrote:
>Unfortunately it is the design of PEAP (and TTLS) to offer separate
>inner and outer identities.
A little Googling seems to reveal that Radiator has a hook that requires the
inner and outer identities to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately it is the design of PEAP (and TTLS) to offer separate
inner and outer identities. There has been a lot of discussion in the
IEEE about how to better support service provider billing in these
instances, but I don't know what came of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How are people handling accounting records for your 802.1X wireless networks?
We're in the process of rolling out EAP-PEAP, and everything is fine in
terms of our RADIUS accounting records from the APs as long as the users
leave the "Outer Identity" f
Does anyone know of a "free" VPN Client for Pocket PC that supports IPSec?
--
Scott Smith
Network Engineering Services
Southern Illinois University Carbondale
[EMAIL PROTECTED]
**
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found
According the manual:
http://www.utstar.com/handsets/manuals/XV6700_manual.pdf
it looks like the XV 6700 supports only LEAP out of the box.
So it looks like SecureW2 is your only other free option. See here:
http://www.securew2.com/uk/forum/viewtopic.php?t=110&highlight=mobile+5
http://www.secur
Yeah, the odyssey software is great. I was trying to avoid the user
from having to pay 50 bucks.We have a site license from Funk for few
odyssey deployments, but those are reserved from clinical PCs. They are
not reserved for users who come in with their own devices.
Lately I have been gett
I have successfully used SecureW2 on several different Windows Mobile 5
devices. It should work. However, if you have problems you might check
out the Juniper (formerly Funk) supplicant, or the supplicant from
Meetinghouse.
However, depending on the device you are using, 802.1X on a Windows
Mobi
Take a look at the Juniper(Funk) Odyssey client software for windows
based phones
-Original Message-
From: Jorge Bodden [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 11:33 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] PocketPC Windows Mobile 5.0
Does anyone
Jorge:
Can you identify which device or wireless card you plan on using? Or are
you looking for any device/wireless that support EAP-TTLS?
Frank
-Original Message-
From: Jorge Bodden [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 10:33 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.ED
Does anyone out there know of a supplicant for a windows 5.0 pocket pc
that will allow for 802.1x authentication using TTLS? Securew2 is only
good for ppc 2003. It would be great if it is a free solution. If not
then I guess the cheapest will have to do.
Thanks.
Jorge Bodden
Network Analy
12 matches
Mail list logo
