kmcuser Auth-Type = LDAP, Huntgroup-Name == "kmc1" Fall-Through = Yes
You probably don't need to force Auth-Type. What freeradius version is this? Why are you using version that is years out of date?
and following lines in /etc/raddb/huntgroup file:
kmc1 NAS-IP-Address == 172.16.0.150
After restarting radius server with radiusd -X, Now if I am trying to logon to NAS device, it is unsuccessfull with following messages:
rad_recv: Access-Request packet from host 172.16.0.150:47715, id=31, length=65 NAS-IP-Address = 172.16.0.155 Service-Type = Login-User NAS-Port-Type = Virtual User-Name = "kmcuser" User-Password = "kmcnet" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "kmcuser", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 modcall[authorize]: module "files" returns notfound for request 0 modcall: leaving group authorize (returns ok) for request 0 auth: No authenticate method (Auth-Type) configuration found for the request: Re jecting the user
That's because you haven't listed ldap in authorize (and your password is in there). Ivan Kalik Kalik Informatika ISP