Multiple instances of custom module
I have a custom module that is working perfectly with FreeRADIUS. I am now interested in creating multiple instances of the module for different NAS's that might be connecting via RADIUS. So from what I gather I can use unlang's switch statement in both the authorize and authenticate sections of the config file like so: authorize { . . switch &request:NAS-IP-Address { case "192.168.1.100" { customer1 } case “192.168.1.110” { customer2 } case { reject } } . . } authenticate { . . Auth-Type CUSTOM { switch &request:NAS-IP-Address { case "192.168.1.100" { customer1 } case “192.168.1.110” { customer2 } } } . . } So my questions are 1) is that the correct way to address multiple instances and 2) is the default case of reject in the authorize section the appropriate way to limit things to the defined instances? r
On 07/04/16 04:26, Richard Levenberg wrote:
I have a custom module that is working perfectly with FreeRADIUS. I am now interested in creating multiple instances of the module for
This isn't a -devel question - best repost on freeradius-users. FWIW yes, this is the right approach and yes, the config and fallthrough to reject looks "right", but it will depend on that policy you want to express.
participants (2)
-
Phil Mayers -
Richard Levenberg