update disconnect and order of operations

[Anatoliy]

Hi Alan , thank you. From default configuration freeradius will try to
resend disconnect message for 30 seconds. So it is possible that all server
threads will be busy with "sending disconnect message" to "bad NAS" and
will drop other accounting requests ?

On Thu, Jul 13, 2023 at 9:36 PM Alan DeKok <aland at deployingradius.com>
wrote:

>
> > On Jul 13, 2023, at 9:57 AM, Anatoliy <cphlpd at gmail.com> wrote:
> > if we receive accounting pack with Class=outage  and DB accessible , we
> > should send disconnect message for this session.
>
>   Yes.
>
> > But, what happens if NAS
> > is busy , or packet will be lost , so we did not receive reply ?
>
>   The basic functionality is documented in sites-available/originate-coa.
>
> > Will
> > freeradius wait for some timeout before continue to linelog directive or
> > sending and processing disconnect message will be executed in parallel
> and
> > we process the linelog without any delay?
>
>   It sends the disconnect request *after* the accounting request is done.
> The server replies to the accounting packet, and then sends the disconnect
> request.
>
>   If there's no response, the disconnect packet is tried a few times.  If
> the NAS never response, the server just gives up on the disconnect.
>
>   Note that this is RADIUS... even if the server could do something when
> the NAS failed to respond to the disconnect packet.  What would the server
> do?  Log something?  You will still need some kind of manual intervention
> to fix things.
>
>   Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>