General question about RadSec implementation on FR 3.2.x

dominic.stalder at unibe.ch dominic.stalder at unibe.ch
Thu Apr 17 11:25:35 UTC 2025


Hi Alan

Thanks a lot, got it.

Regards


Am 17.04.25, 13:22 schrieb "Freeradius-Users im Auftrag von Alan DeKok" <freeradius-users-bounces+dominic.stalder=unibe.ch at lists.freeradius.org <mailto:unibe.ch at lists.freeradius.org> im Auftrag von aland at deployingradius.com <mailto:aland at deployingradius.com>>:


On Apr 17, 2025, at 2:24 AM, <dominic.stalder at unibe.ch <mailto:dominic.stalder at unibe.ch>> <dominic.stalder at unibe.ch <mailto:dominic.stalder at unibe.ch>> wrote:
>
> Hi Alan
>
> Thanks for the fast and informative feedback. When I get your answer correct, I can just can put:
>
> 1. all RADIUS [UDP] & RadSec [TCP] clients into clients.conf and it does work
>
> 2. all RADIUS [UDP] & RadSec [TCP] home servers into proxy.conf and it does work
>
> So I can "consolidate" all clients and all home servers in one location respectively?


Yes.


The file names don't matter. All of the files are merged into one via $INCLUDE statements. So you can add clients to the bottom of a virtual server file if you want.


What matters is the sections. If you put clients into a "name { ...} " section, then they won't be found. Each section has a pre-defined purpose, and a pre-defined content.


Alan DeKok.


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <http://www.freeradius.org/list/users.html>





More information about the Freeradius-Users mailing list