Thansk you Alan for your reply We have tested with JAVA script, to send a Calling Station ID, and its work fine with the Checkval . That mean all NAS must be configure to send alone their Calling Station ID ? The Radius exchange between the Proxy don't ask this needed info? Regards 2017-07-18 13:34 GMT+02:00 Alan DeKok <aland@deployingradius.com>:
On Jul 18, 2017, at 3:21 AM, Karim Bourenane <karim.bourenane@gmail.com> wrote:
My goal is to validate the user/password from the MAC addresss and IP Adresse for several network name identified in the user Ldap account.
I'm not sure why there's an issue. You configured the module to use Calling-Station-Id, and then sent it a request which doesn't contain Calling-Station-Id.
*And the output from the Radius Server Backend*:(plugged with the local Ldap) rad_recv: Access-Request packet from host 10.166.120.43 port 38694, id=96, length=102 User-Name = "idtestradius2@CUSTOMER1" User-Password = "testradius" NAS-IP-Address = 10.166.120.43 NAS-Port = 0 Message-Authenticator = 0xf0d7406bbd8e56ca8c40403578dbf4f0 Event-Timestamp = "Jul 18 2017 09:07:08 CEST" Proxy-State = 0x3633 ...
Tue Jul 18 09:07:08 2017 : Debug: rlm_checkval: Could not find item named Calling-Station-Id in request Tue Jul 18 09:07:08 2017 : Info: ++[checkval] = reject
What part of that is unclear?
If you want to use Calling-Station-Id, send an Access-Request which contains Calling-Station-Id.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
-- Mr Karim Bourenane +33686464439