Hello Doug -
I don't think anything ever came of that discussion.
However, you could fairly easily build a tunnel between the NAS and the
Radiator host and route the radius packets across it. Kind of a band-aid
solution though.
Note that there is a lot of work going on at present on the next
I was referring to this post:
http://www.open.com.au/archives/radiator/2001-05/msg00335.html
Unfortunately our wish list for reliable accounting pretty much says it all.
We would like end-to-end reliability from the NAS to the SQL server. I know
that's a tall order, and I was asking more in a c
Hello Doug -
Sadly, at this point in time "reliable accounting for Radius" is a
contradiction in terms, due to the use of UDP for one thing and the odd NAS
software bug for another.
Perhaps you could give me a bit more detail on your requirements?
regards
Hugh
On Fri, 31 May 2002 02:59, D
On Fri, 1 Jun 2001 [EMAIL PROTECTED] wrote:
> We have serious problems with acct. requests that are lost.
>
> Actually we use scripts made by us to check really-used ports and delete
> incorrect entries in RADONLINE table.
We also have quite a bit of trouble with stale data in the RADONLINE
tabl
Hello Mariano,
On Jun 1, 6:47pm, Mariano Absatz wrote:
> Subject: RE: (RADIATOR) Reliable accounting?
> Hi Mike, Julio
>
> I guess I don't fully understand what's beeing discussed.
Typically its packet loss in transit between a proxy Radius server and the main
radiu
Hi Mike, Julio
I guess I don't fully understand what's beeing discussed.
Mike, how do you expect to do reliable UDP between Radiator and "something-
else", this being a NAS, or a proxying or proxied Radius server, when you can
only change Radiator?
Or is there something called "reliable radius
Hi Mike,
as Julio, we have problems with lost request too, and we correct the
RADONLINE/NASES mismatches with scripts, accesing the sql db
directly.
so, if you want, we could work with you testing your code.
regards
On Fri, 1 Jun 2001 12:20:32 +0200, [EMAIL PROTECTED] wrote:
>Hello Mike,
>
>W
Hello Mike,
We have serious problems with acct. requests that are lost.
Actually we use scripts made by us to check really-used ports and delete
incorrect entries in RADONLINE table.
The frequency of the executions of these scripts is high. And they use
radpwtst to correct bad entries in RADONL
