MySQL Client Issue

[Selahattin CILEK]

On 09.09.2023 23:44, Alan DeKok wrote:
> On Sep 9, 2023, at 4:03 PM, Selahattin CILEK <selahattin_cilek at hotmail.com> wrote:
>> I have been installing FreeRADIUS 3 on pfSense for about out 5 years and it always came bundled with some version of *mysql57-client* (this or that minor version) and it always worked well with *mysql57-server* (again, this or that minor version), which FreeRADIUS connected to. To give you a context, the last time I installed was about a month ago and the versions were as follows:
>> ...
>> But the guys at pfSense decided to skip version 13 of FreeBSD and build version 2.7.0 on FreeBSDversion 14. The 2.7.0 version of pfSense comes with *freeradius3-3.2.2* and *mysql80-client-8.0.32_2* . Of course, I could just install *mysql80-client-8.0.32_2* and modify my SQL code a little bit and it would still work. But the problem is that I have Syslog-NG installed on the system and it too connects to the same MySQL instance and though it has been upgraded to version 4.20, it still uses the old *mysql57-client. *
>    Why doesn't syslog-ng use the newer MySQL client library?
That's a good question, I have been wondering that myself too. Maybe 
they don't want to break anything by upgrading to the newer DB client. 
Who knows...
>
>> So is there a way to get FreeRADIUS 3.2.2 to work with the old MySQL client, you know, using the good old "libdbi" driver?
>    You can build it from source.
Where would one start? Could you point to a specific direction?
>
>    In general it's not a good idea to have multiple versions of the same library on a system.  All kinds of things can go wrong.
>
>    Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com