On 23/09/2022 18:05, Steven Walters wrote:
Thanks for the response Nick. I tried version first 3.0.26 but had an issue with the openldap driver on RHEL7 when trying to start freeradius. As we are running RHEL7 I decided on the highest version available from the RHEL7 repo, which is 3.0.13. As the instructions on packages.networkradius.com state, you need the LDAP Toolbox Project repository as well as the Network RADIUS one on RHEL 7 - this is due to RedHat compiling their LDAP libraries against NSS rather than OpenSSL I confirmed no freeradius is not running in the background. If I remove all the sites except default and inner-tunnel, freeradius starts fine.
If FreeRADIUS is unable to bind to port 1812, then something else is bound to that port. Try sudo ss -lunp | grep 1812 to see what is bound to that port.
With the following sites enabled no start.
[root@radius-02.cnt sites-enabled]# ls -ltr total 0 lrwxrwxrwx. 1 root radiusd 26 Sep 22 11:36 default -> ../sites-available/default lrwxrwxrwx. 1 root radiusd 31 Sep 22 11:36 inner-tunnel -> ../sites-available/inner-tunnel lrwxrwxrwx. 1 root root 25 Sep 23 18:38 mobile -> ../sites-available/mobile lrwxrwxrwx. 1 root root 34 Sep 23 18:38 staticipaddress -> ../sites-available/staticipaddress
With only the following sites-enabled, freeradius starts. The same configs that worked under 3.0.1 with no issue.
[root@radius-02.cnt sites-enabled]# ls -ltr total 0 lrwxrwxrwx. 1 root radiusd 26 Sep 22 11:36 default -> ../sites-available/default lrwxrwxrwx. 1 root radiusd 31 Sep 22 11:36 inner-tunnel -> ../sites-available/inner-tunnel
Default, mobile and staticipaddress using the same protocols (1812 auth and 1813 acct) and "ipaddr=*" for all three.
Kind Regards Steven
-- Nick Porter