problem in configuring PEAP on freeRADIUS1.1.2

[Pradeep Sengar]

Thanx Zoltan Ori for ur comments. before getting ur reply i was able to run
freeradius server for peap after making following changes in eap.conf file
in tls module
xxxxxxxxxx
eap.conf
xxxxxxxxxx
tls {

                        private_key_password = whatever
                        private_key_file = ${raddbdir}/certs/cert-srv.pem

                        certificate_file = ${raddbdir}/certs/cert-srv.pem


                        CA_file = ${raddbdir}/certs/demoCA/cacert.pem

                        dh_file = ${raddbdir}/certs/dh
                        random_file = ${raddbdir}/certs/random

                 }
xxxxxxxxxxxxxxxx eap.conf ends herexxxxxxxxxxxxxxxxxxxxxxxx

problem persisted till i added last line( random_file =
${raddbdir}/certs/random) and started working fine after this addition
without creating any certificate(i didn't create any).

but after this although i m able to start server but its not accepting any
requests.
What can be the reason?

One more query: in clients.conf file we mention the IP range for APs or for
end client(supplicant).

Regards
Pradeep Singh






Date: Wed, 5 Jul 2006 09:33:14 -0400
From: Zoltan Ori <z.ori at morehead-st.edu>
Subject: Re: problem in configuring PEAP on freeRADIUS1.1.2
To: FreeRadius users mailing list
        <freeradius-users at lists.freeradius.org>
Message-ID: <200607050933.14945.z.ori at morehead-st.edu>
Content-Type: text/plain;  charset="iso-8859-1"

On Wednesday 05 July 2006 08:48, Pradeep Sengar wrote:
> rlm_eap_tls: Loading the certificate file as a chain
> rlm_eap: SSL error error:0200100E:system library:fopen:Bad address
> rlm_eap_tls: Error reading certificate file
> rlm_eap: Failed to initialize type tls

Did you create any certificates? Are they stored where you indicate in
eap.conf? Do they have the proper permissions?

Zoltan Ori



--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20060706/5f2bdaed/attachment.html>