[RADIATOR] FW: FW: RADIATOR: EAP-FAST-MSCHAPv2

Heikki Vatiainen hvn at open.com.au
Mon Apr 16 03:02:51 CDT 2012


On 04/16/2012 08:25 AM, Sudhir Harwalkar wrote:

> When radius server gets restart, our device sending same PAC details, it should authenticate right?
>  because for the radius server it's the new key when it get restart, it has to authenticate if radius server is not remembering the previous keys info , please correct me if I have Understood wrong.

Currently Radiator will provision a new PAC if the PAC is unknown or too
old. The behaviour should be the same when the client sends no PAC at all.

You should check the client you are using to see how it reacts when the
PAC it sends is not accepted a new PAC is provisioned.

Thanks!
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

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.


More information about the radiator mailing list