Different authorize files for virtual servers
This should be easy. I'm sure I'm missing something obvious. I want to run two virtual servers bound to different ports with each one consulting a different "authorize" file. The "files" module seems bound to whatever is in mods-enabled/files, which I can obviously change but that changes it for both servers. Attempts to teach the files module a different path have failed with various errors. Is there an example of this somewhere? I could obviously run two completely separate instances of freeradius (3.0.16 on Slackware Linux) but that seems silly. -- Jay Rouman (jsr@edzone.net) Gratiot/Isabella RESD, Ithaca, MI
On Sat, 2018-03-24 at 14:52 -0400, Jay Rouman wrote:
This should be easy. I'm sure I'm missing something obvious.
Yes :)
I want to run two virtual servers bound to different ports with each one consulting a different "authorize" file. The "files" module seems bound to whatever is in mods-enabled/files, which I can obviously change but that changes it for both servers.
Define two instances of the files module with appropriate config for each virtual server: files files1 { ... } files files2 { ... } Then in one virtual server call "files1", and in the other call "files2". There are examples for other modules, e.g. in "raddb/mods- available/detail.log". -- Matthew
participants (2)
-
Jay Rouman -
Matthew Newton