"Module ... became unblocked" after FR30 upgrade

Alan DeKok aland at deployingradius.com
Wed Jun 22 15:04:14 CEST 2016

On Jun 22, 2016, at 5:57 AM, Jakob Hirsch <jh at plonk.de> wrote:
> Ok, probably found the cause: A radius client (RADIUS proxy from one of
> the wholesale providers we use) sometimes sends two consecutive
> accounting requests with the same request id (and from the source
> ip/port),

  Then it's broken.

> so FR ignores the second request as a duplicate and won't send
> an Accounting-Response. The log message then looks like this:
>> Error: Received conflicting packet from client xxxx_acct3 port 20001 - ID: 143 due to unfinished request.  Giving up on old request.
>> WARNING: (3134530) WARNING: Module rlm_preprocess became unblocked for request 3134530

  That message really should really describe the underlying problem, but that's not a trivial fix.

> Strangely, I don't get the "Module ... became unblocked" for _all_ of
> these false duplicates, but _every_ "became unblocked" log entry is
> preceded by "Error: Received conflicting packet...".

  That's the problem, thn.

> Obviously, this is bad and wrong behaviour of the radius client, so I'll
> try to get them to fix this.

  Yes.  If they fix it, the problem will go away.

  Alan DeKok.

More information about the Freeradius-Users mailing list