Hi,
1. Whenever I flash the new code to the device it's generating new PAC key at
that time it's getting authenticate with the server,
If PACs are gone after a restart, but our device generating the same and
send to the server so it should authenticate, why that's not happening here.
2. For EAP-TLS I took CA Certificate from
C:\Radiator\Radiator-Locked-4.9\certificates\demoCA \cacert.pem and for Client
I used C:\Radiator\Radiator-Locked-4.9\certificates\ cert-clt.pem is these are
the correct files that I am using.
Sudhir H
-----Original Message-----
From: Heikki Vatiainen [mailto:[email protected]]
Sent: Thursday, April 12, 2012 2:52 PM
To: Sudhir Harwalkar
Subject: Re: FW: [RADIATOR] FW: RADIATOR: EAP-FAST-MSCHAPv2
On 04/12/2012 09:25 AM, Sudhir Harwalkar wrote:
> Thanks for helping me Heikki, when I flash the new code, then start the
> radius server it's working fine after that I restarted the radius server and
> power on the device then it's not authenticated.
> Again I flash the code and verified working fine.
Ok. Good to hear it works.
> Problem arises only if I restart the radius server.
> This should not happen right.
By default Radiator keeps PACs in memory and they are gone after a restart.
There is a possibility to keep them in SQL so that they survive across reboots.
Heikki
Larsen & Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended
recipient (s) If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.
_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator
