Date: Wed, 19 Nov 2003 14:08:39 +0500 From: Boris Kovalenko <boris@ntmk.ru> To: Michael Bretterklieber <mbretter@a-quadrat.at>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: ppp RADIUS accounting bug Message-ID: <3FBB3317.4090001@ntmk.ru> In-Reply-To: <Pine.WNT.4.58.0311190932020.1928@BRUTUS> References: <3FBAEAC1.7090709@tagnet.ru> <20031119071703.GA38863@pit.databus.com> <3FBB1DF3.1050706@ntmk.ru> <Pine.WNT.4.58.0311190851470.1928@BRUTUS> <3FBB2743.8040508@ntmk.ru> <Pine.WNT.4.58.0311190932020.1928@BRUTUS>
next in thread | previous in thread | raw e-mail | index | archive | help
>The RFC says:
>
>5.4. Acct-Output-Octets
>
>blabla
>
>can only be
> present in Accounting-Request records where the Acct-Status-Type
> is set to Stop.
>
>It looks like, that these counters must not present in accounting updates.
>
You are right, but your words - "but a patch could be written :-)".
Again, I'm talking not about UPDATE packets and presence of any
attributes in RADIUS requests. I'm talking about wrong handling of
Acct-Input-Octets & Acct-Output-Octets with current PPP RADIUS
implementation. How this will be done, by implementing RFC2869 support
or just by resending STOP request N times is not so important, but
somehow this should be done. I may try to write patch myself, but I'm
looking for someone who supervises my patch and commit it if no problems
will be founded.
Regards,
Boris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FBB3317.4090001>