Handling FreeRADIUS software upgrades

[George Benjin]

Hi All,

In each of our FreeRADIUS installations, We have removed the default
and inner-tunnel symlinks in the sites-enabled directory. We've also
removed the default EAP symlink in the mods-enabled directory.

We have left the original files in the 'available' directories for
reference but we're using our own virtual server and eap module
configurations, e.g.

- parent-company site, parent-company-inner-tunnel site,
eap-parentcompany module.
- child-company site, child-company-inner-tunnel site, eap-childcompany module.

This was running very well until we encountered a brief interruption
on one of the servers when the recent RHEL package update for
FreeRADIUS 3.2 was applied.


The update re-added the default & inner tunnel site symlinks, as well
as the default eap module symlink which resulted in the service not
functioning as intended.

We resolved this quickly by deleting the symlinks again but this will
probably happen again with a future update.

What changes should we make to our config to avoid this happening
again? Delete the default files in the 'available' dirs? Replace them
with dummy content? Copy dummy files into the sites-enabled and
mods-enabled dirs?

Cheers