Re: Dynamic Attributes Based on NAS Type !
Stefan A. wrote:
What would you recommend to do, if your client is a proxy server? NAS-ID?
No. Don't send policies back. You don't control the NAS. So you have no business sending it NAS-specific policies.
Nice idea, as long as a NAS vendor does not introduce another or additional way(/attribute) to do things in never NAS OS Versions. In that case you would possible get in trouble if you have both NAS OS versions in your network and feed them with mixed attributes. Starent did this in the past, where they had a bunch of QoS attributes in one Version and a single Attribute (177) to handle them all at once in never versions.
Yes, well, NAS vendors have been known for doing weird things. Hence RFC 6158. Alan DeKok.
Alan wrote:
What would you recommend to do, if your client is a proxy server? NAS-ID?
No. Don't send policies back.
You don't control the NAS. So you have no business sending it NAS-specific policies.
I never talked about sending policies to the NAS. The question was, what would be the recommendation, if the RADIUS client is a RADIUS Proxy server (..in between the original NAS and my FR...) In that case, "%{client:nas_type}" won't work, because it would always be the same (... proxy server....) Would one use "%{NAS-ID}" instead of "%{client:nas_type}"? Stefan
participants (2)
-
Alan DeKok -
Stefan A.