I made all the changes you have mentioned, then I run the config file, in the
log file I got message as follows
Thu Mar 22 15:00:17 2012: DEBUG: Finished reading configuration file
'c:\Program Files\Radiator\radiusnew.cfg'
Thu Mar 22 15:00:17 2012: DEBUG: Reading dictionary file
'C:\Program Files\Radiator/dictionary'
Thu Mar 22 15:00:17 2012: DEBUG: Creating authentication port
0.0.0.0:1812
Thu Mar 22 15:00:17 2012: DEBUG: Creating accounting port
0.0.0.0:1813
Thu Mar 22 15:00:17 2012: NOTICE: Server started: Radiator 4.9
on EMMYS0938 (LOCKED)
Is this authenticated with AP?
As you mentioned I haven't got message like receives from AP.
Regards
Sudhir H
-----Original Message-----
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Behalf Of Heikki Vatiainen
Sent: Thursday, March 22, 2012 2:22 PM
To: radiator@open.com.au
Subject: Re: [RADIATOR] Radiator
On 03/21/2012 03:58 PM, Sudhir Harwalkar wrote:
> Thanks a lot for helping me out.
> I have one query :
> Steps that I followed for EAP-PEAPv0 Testing:
> 1. Copied eap_peap.cfg file to c:\program file
Add a Client clause with your AP's address in the configuration. Also set DbDir
and LogDir as I just mentioned in my other message:
LogDir c:/Program Files/Radiator
DbDir c:/Program Files/Radiator
> 2. in the command line I typed the command "perl radiusd
> -bind_address 192. . . . -auth_port 1812 -log_file filename
> -config_file c:\program files\eap_peap.cfg When I run this command I
> am getting an error, the error details are shown in the screenshot
> named as eap_peap.PNG
You do not need to set BindAddress. If set, it should be address belonging to
your computer, not to the AP. You usually do not need to set this at all.
> - Is there anything that I need to make change?
Please see above.
> -How does we know that communication happening between AP and Radius Server?
The log will messages Radiator receives from AP.
> -Port address that I have given in AP is 1812 is that right?
Please see above. About auth_port, it should match the setting in AP. By
default Radiator uses 1645 so you need to check both AP and Radiator use same
port number.
> -please see the config file that I have used is attached with this mail.
I suggest you try seeing simple authentication without PEAP works before moving
to PEAP configuration. If your AP provides a method to authenticate users with
plain username and password (no PEAP involved), this would be the best method
to see the basic communication between AP and Radiator works.
Thanks!
Heikki
>
> Thanks
> Sudhir H
>
>
> 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
> radiator@open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
--
Heikki Vatiainen <h...@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.
_______________________________________________
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
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
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
