Freeradius Module Extension Magic Number mismatch

[Alan DeKok]

On Sep 9, 2024, at 11:41 AM, Dincer Beken <dbeken at blackned.de> wrote:
> Freeradius 3.2.1 is installed from debian packages (standard debian bookworm distribution). I have implemented a new module and added it as an .so. I built the module alongside Freeradius 3.2.1 (from github).
> 
> When enabling the module, I get the following error:
> 
> 
> Mon Sep  9 15:29:38 2024 : Error: /etc/freeradius/3.0/mods-enabled/tba[1]: Failed loading module rlm_(null) from file /usr/lib/freeradius/rlm_tba.so
> Mon Sep  9 15:29:38 2024 : Error: /etc/freeradius/3.0/mods-enabled/tba[1]: Application and rlm_(null) magic number (prefix) mismatch.  application: 0 module: f0
> Even if I write the simplest module, I get this issue.

  The module API changes occasionally.  So instead of having the server crash when something is misconfigured, it checks the magic number and complains.

> The has the following binder. Can you tell me, where the issue is originating from, and how I can get the MAGIC number? I searched and tried out a lot, but at the end, had to implement the functionality as a python script. Getting the radius module running would help me a lot.

  The magic number is part of the build process.  You have to build all of the modules and server core at the same time.

  i.e. you can't install a version of FreeRADIUS from packages, and then try to add your own module to it.  You will get the error you see above.

  Alan DeKok.