Alan DeKok <aland@deployingradius.com> writes:
Bjørn Mork wrote:
My problem is that the configuration seems a bit clumsy, given that I cannot really change neither IP address nor secret from what's already there in the FreeRADIUS client definition. It would have been ideal to just add a flag or whatever, saying that "this client is also a CoA server", and allowing direct proxy to it using some virtual attribute.
Hmm.. so that would re-use the normal client IP && shared secret for CoA servers?
Yes, that would Just Work.
Is this a correct view of the current (2.1.x) state of CoA proxying, or did I miss something?
It's pretty much correct.
I believe I saw a request for dynamic home servers recently. Looks like that might be something for me as well.
Maybe. Or, having less work to say "this client can also receive CoA requests".
That might be easy to add for 3.0.
Thanks for the encouraging answer. Such a feature would probably be useful for other types of NASes with CoA servers as well. Bjørn