tls: Using cached TLS configuration from previous invocation

Alan DeKok aland at
Tue Jan 23 02:12:54 UTC 2024

On Jan 22, 2024, at 8:45 PM, Jack Carter <jack_carter94 at> wrote:
> I’m pretty new to FreeRADIUS but so far it’s working well for me. I have been running it on a Raspberry Pi 4 running Bookworm (FreeRADIUS Version 3.2.1) but wanted to run on my two HA Raspberry Pi Network Tools Pi 3B+’s running Bullseye (FreeRADIUS Version 3.0.21).

  That should be fine.

> Config had been running great on the Pi 4 so I copied the contents of the following and pasted it into the same files running on the Pi 3.
> /etc/freeradius/3.0/mods-enabled/eap
> /etc/freeradius/3.0/clients.conf
> /etc/freeradius/3.0/users
> All seems well and when I test the PEAP config for my WiFi it all works as expected… however, I am seeing the below logged in the service status which differs considerably from the Pi 4. Why would it not be taking my TLS config and instead using the cached from previous invocation?

  It's just logging what it's doing so that the reader knows where the various TLS configuration came from.

> Do I need to be worried or is everything running as it should?

  Does it say "error"?  No?

  It's fine.  

  Alan DeKok.

More information about the Freeradius-Users mailing list