Radius Not Entering Modules Placed After Mod_Null

(Doc ID 1057922.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: - Release: 7.3.1
Information in this document applies to any platform.


Having the following configuration in Radius:

auth_terminator {

example_log {
check {

Radius is not calling the custom module mod_example. The reason for sending response to network first, and then process requests, is that network doesn't need to wait till we process logic in mod_example, before getting the response.

That applies not only to custom modules. If the mod_proxy module is placed after mod_null, Radius is not calling mod_proxy. The need in this case is to forward a request to another Radius server using mod_proxy, so the expectation is to send a response before mod_proxy.

Why modules placed after mod_null in the module chain aren't called?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms