This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| getting_started:20_install_ubuntu_freeradius_3 [2021/01/22 21:31] – [Introduction] admin | getting_started:20_install_ubuntu_freeradius_3 [2022/01/14 14:14] (current) – [Next steps] admin | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| sudo mv / | sudo mv / | ||
| sudo chown -R freerad. / | sudo chown -R freerad. / | ||
| + | sudo mkdir / | ||
| + | chown freerad. / | ||
| </ | </ | ||
| * Configure the site-wide shared secret. This will be the value used by ALL Dynamic Clients. | * Configure the site-wide shared secret. This will be the value used by ALL Dynamic Clients. | ||
| Line 75: | Line 77: | ||
| sudo systemctl status freeradius | sudo systemctl status freeradius | ||
| </ | </ | ||
| + | |||
| + | ===== Fixing a small bug ===== | ||
| + | |||
| + | * There is a small bug which prevents FreeRADIUS to start up after a reboot. | ||
| + | * It has been reported here: https:// | ||
| + | * There also seems to be a fix but it has not reached the Ubuntu repositories as of this writing. | ||
| + | * So here is the fix taken from the discussion in the link | ||
| + | * Create a file called **/ | ||
| + | <code bash> | ||
| + | sudo vi / | ||
| + | </ | ||
| + | * Add the following line | ||
| + | <code bash> | ||
| + | d / | ||
| + | </ | ||
| + | * If you are curious about what we did, here is a writeup on **tmpfiles.d** | ||
| + | * https:// | ||
| + | |||
| + | |||
| ===== Add Nginx to run scripts ===== | ===== Add Nginx to run scripts ===== | ||
| * To create the ability for the web server to exercise some control over FreeRADIUS, we will have a custom script which is added to the** sudoers** file. | * To create the ability for the web server to exercise some control over FreeRADIUS, we will have a custom script which is added to the** sudoers** file. | ||
| Line 91: | Line 112: | ||
| </ | </ | ||
| * This will allow the root user in RADIUSdesk to Start and Stop FreeRADIUS service and do on-the-fly activation of debug traces. | * This will allow the root user in RADIUSdesk to Start and Stop FreeRADIUS service and do on-the-fly activation of debug traces. | ||
| + | |||
| + | ===== Next steps ===== | ||
| + | * You need to do a few small tweaks for your environment | ||
| + | * The first part of the instructions if specific to the Raspberry Pi. You can skip them and go to the **Adapt The Settings In MESHdesk** section if you are running RADIUSdesk on something else. | ||
| + | * [[md: | ||