I dont know if there is a issue , but as you can see: example config file ippool: /ippool main_pool { / /filename = ${db_dir}/db.ippool/ /}/ Config base radiusd.conf: /raddbdir = /etc/freeradius/ /db_dir = ${raddbdir}/ /$INCLUDE ${raddbdir}/mods-enabled// I have not configured to write in /etc , this is by default , as you can see example config file ippool module , and base config of freeradius in radiusd.conf , vars point to /etc/freeradius folder, that folder is writable by freerad user. / / //etc# ls -ls | grep freeradiu 4 drwxr-s--x 9 freerad freerad 4096 Jul 10 13:01 freeradius/ And yes , its a bad idea , but default config have this config point to /etc/freeradius , so .. by default it must run , whatever if you test all that and runs , I can point that DB files to another folder as you recoomended me. I go to test it on another folder by the way , but I dont think this is the problem with this issue El 10/7/24 a las 14:07, Alan DeKok escribió:
On Jul 10, 2024, at 7:16 AM, Rubenb<rubenb@verdnatura.es> wrote:
Im using freeradius 3.2.4 , I have a problem that I couldn't set up ippool module. When I do a symbolic link with mods-enabled and mods-available of ippool module , I set up ippool module with two pools.
Then when I go to start the service freeradius with systemd , it couldnt start , syslog says:
/"rlm_ippool: Failed to open file /etc/freeradius/db-users.ippool: Read-only file system" That seems fairly clear.
This isn't a problem with FreeRADIUS. You've configured FreeRADIUS so that it tries to write files to /etc, but /etc isn't writable.
So... configure FreeRADIUS to write files somewhere else, which is writable.
And in general, it's a bad idea to put DB files into /etc. They usually go into a writable directory, like /var.
Alan DeKok.
- List info/subscribe/unsubscribe? Seehttp://www.freeradius.org/list/users.html
--