See responses below: -- Neil Johnson Network Engineer The University of Iowa Phone: 319 384-0938 Fax: 319 335-2951 Mobile: 319 540-2081 E-Mail: [email protected]
On 5/15/12 12:50 PM, "Heikki Vatiainen" <[email protected]> wrote: >On 05/15/2012 01:02 AM, Johnson, Neil M wrote: > >> I have been testing TLS Session Resumption and found that when I moved >>the >> RADIATOR configuration from 32-bit Windows Server 2003 R2 to 64-bit >> Windows Server 2008 R2 that it stopped working. The wireless controller >> reports a time-out during the 1st phase of the for way handshake. > >Thanks for the logs. A couple of questions: >- Is that a cisco controller (wlc)? No, we have Meru http://www.merunetworks.com >- If you have more than one type of WLAN equipment (controllers, APs), >does session resumption work with any of them Nope, we only have Meru equipment. >- Can you get log from the wireless client? What kind of log are you talking about ? I tried running a trace with the command "netsh wlan tra on" but it didn't generate the log files I was expecting. > >Do you have this in the config: >EAPTLS_PEAPVersion 0 Yes. The major difference seems to be the OS Radiator is running on. It seems to work on Windows Server 2003 R2 (32-bit), but not on Windows Server 2008 R2 (64-bit). Thanks > >Thanks! >Heikki > >-- >Heikki Vatiainen <[email protected]> > >Radiator: the most portable, flexible and configurable RADIUS server >anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, >Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, >TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, >DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, >NetWare etc. >_______________________________________________ >radiator mailing list >[email protected] >http://www.open.com.au/mailman/listinfo/radiator _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
