Well this has turned out to be some sort of linkage/compile issue. On the same server, I can build the shared library for our module from either the source tree from our application or the source tree from freeradius. Building from freeradius works. The other way does not... Best I can tell the same includes and libraries are used. A ldd of both .so files show commonality though our app has many more referenced libraries. I wonder if we've got a namespace collision somewhere. Anybody got a suggestion for where to look? Bill On 4/17/2014 9:19 PM, Alan DeKok wrote:
Bill Schoolfield wrote:
We have written a custom accounting module based on rlm_detail. It is very similar except it pushes the accounting data to another app via an API call. Up until recently it has work fine.
I'd suggest looking at rlm_rest in v3. It allows for remote json calls. It's really quite nice.
Today on a client site it is failing. It seems the "accounting method":
static int modulename_accounting(void *instance, REQUEST *request)
is getting passed with a request that has at least (I haven't checked further) null request->packet and request->listener addresses.
That should never happen.
The request is generated via radclient.
Does anyone know under what circumstances this can occur? Happy to provide all details/source etc if it will help.
It only happens when the request is freed, while it's still being processed by a module. That should never happen, either.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html