RE: Fall-through and different NAS IP Settings
I'm just asking this for my understanding, am I still going to want to >>use Client-IP-Address even though from what I can see here, the NAS-IP- Address attribute is appearing within the output of debugging?
I would suggest using Client-IP-Address, unless you know that the NAS will always send that attribute with that value.
As for why it doesn't match, I'm not sure. Try editing the "users" file entry to see if you can narrow down the problem.
How do you explain this then? I have a NAS that DOESN'T sent NAS-IP-Address attribute to the radius server (only nas-identifier) but all my huntgroups based on NAS-IP-Address work without any problem... Is this then somewhere in the code? If (!NAS-IP-Address && Client-IP-Address) NAS-IP-Address = Client-IP-Address J. -- Jonathan De Graeve Network/System Administrator Imelda vzw Informatica Dienst 015/50.52.98 jonathan.de.graeve@imelda.be
Jonathan De Graeve wrote:
How do you explain this then?
I have a NAS that DOESN'T sent NAS-IP-Address attribute to the radius server (only nas-identifier) but all my huntgroups based on NAS-IP-Address work without any problem...
Is this then somewhere in the code?
If (!NAS-IP-Address && Client-IP-Address) NAS-IP-Address = Client-IP-Address
J.
Yes. rlm_preprocess adds the nas-ip-address to the request if one wasnt there. I have patched my local freeradius to add Client-Ip-Address if it is missing and Client-Short-Name (local creation) as well. Joe
participants (2)
-
Joe Maimon -
Jonathan De Graeve