ippool: not found -> not sending reply

Alan DeKok aland at deployingradius.com
Tue Dec 27 21:02:22 UTC 2022

On Dec 27, 2022, at 10:53 AM, Volodymyr Litovka via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
> Hi,
> I have in 'users' two kinds of users - one with static IP assignments (Framed-IP-Address) and one with ippool. The issues comes with those 'static' users - when accounting stop happens, ippool behaves in the following way:

  The solution is to not run the ippool module for static IPs.

> it _looks_ as it has no consequences except timeouts and resends on NAS side, but I don't like error-like behaviour. So I was able to fix this with the following statement in 'accounting' section (which is responsible for freeing the lease):
>         redundant {
>                 main_pool
>                 ok
>         }

  Or better:

	if (notfound) {

  That was if the ippool module returns "fail", the packet will still fail.

> so regardless of main_pool's error, always return ok.
> But I have a question - while this is not leasing, but freeing of the lease, whether such rough override can impact something else? Whether it's make sense to add more granular control like "if main_pool returns notfound then it's ok" ? And, sorry for this - how it can be written using unlang?

  Every module is independent.  So if one module doesn't do anything, it doesn't affect anything else.

  Alan DeKok.

More information about the Freeradius-Users mailing list