We are going to have multiple VPN servers running on Debian 10. Each server has its own freeradius installation connecting to a central Freeradius database. More servers will be added to the pool in future. If each future installation gets the latest freeradius copy, a schema change could break it when trying to communicate to the central freeradius database, that has now an older schema. Ideally we need to freeze all future installations to a specific version, even if newer versions get to be released. The current base version on Debian 10 is 3.0.17, which is pretty old. Hence I was hoping there was a way to freeze it to 3.0.21 for all our future installations. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, 14 March 2021 13:48, Alan DeKok <aland@deployingradius.com> wrote:
On Mar 14, 2021, at 7:38 AM, Mark Antony via Freeradius-Users freeradius-users@lists.freeradius.org wrote:
Based on Freeradius website, it is possible to echo "deb https://packages.networkradius.com/releases/debian-buster buster main" >> /etc/apt/sources.list sudo apt-key adv --keyserver keys.gnupg.net --recv-key 0x41382202 apt update But it doesn't allow me to install the older version 3.0.20: apt install --only-upgrade freeradius=3.0.20
We don't keep older copies of the packages around.
Is there any reason you don't want to install the latest version?
Alan DeKok.