Hello Arthur -
Radiator operates as a Diameter to RADIUS translation gateway.
That is to say that incoming Diameter requests are converted to RADIUS requests
that are processed in the normal way.
So yes, if your frontend has a clause it will translate the
Diameter requests to RADIUS requests
Hello Adrian -
It looks like you have not correctly installed the prerequisites for ADSI.
See section 5.41 in the Radiator 4.6 reference manual ("doc/ref.pdf").
If you are running on Windows I suggest the AuthBy LSA clause instead, which is
much more flexible.
See section 5.51 in the manual.
* Hi:
I'm configuring radiator to use ADSI Authentication as indicated below:
*
RewriteUsernames/^([...@]+).*/$1/
# Adjust DBSource, DBUsername, DBAuth to suit your DB
DBSourcedbi:ODBC:MyDatasource
DBUsernamemyusername
DBAuth mypassword
Accou
Thread name changed, because I'm interesting does Diameter works with
Radiator proxy environment.
Say, one instance runs as proxy with 'AuthBy *BALANCE' and others in the
different ports as child instances.
Without Farming.
br,
Arthur
Heikki Vatiainen wrote:
> On 08/06/2010 02:12 PM, Arthur Ko
On 08/06/2010 02:12 PM, Arthur Konovalov wrote:
> Does proxy will work with DIAMETER protocol too?
Server farming was mentioned in this thread, so I thought I would say
something about Diameter and farming. From experience I can tell that
Diameter works with server farm. Since Diameter runs over
Thank You for explanation.
Does proxy will work with DIAMETER protocol too?
br,
Arthur
> The frontend simply proxies the requests with an "AuthBy *BALANCE" to the
> backends where the processing occurs.
>
> You would set up multiple backends on different port numbers such that all of
> your pr
Hello Arthur -
Well if you only use FarmSize on its own, the children will round-robin taking
packets from the socket queue.
In your case I see you are only processing accounting requests, so I am
guessing that if you only process accounting starts and accounting stops, two
of the processes a
OK,
it's clear now. Thank You.
> The parent process does not handle any RADIUS requests itself, so although
> you have increased the debug level for the parent process, the children are
> still running at Trace 3.
>
>
BTW, about Farming. It's unclear for me from CPU load aspect. My
Radiator
Hello Arthur -
When you specify "FarmSize 4" in your configuration file, you are telling
Radiator to start 4 child processes, all of which listen on the AuthPort and
AcctPort you have specified.
The parent process does not handle any RADIUS requests itself, so although you
have increased the
Hi!
Please correct me if I'm wrong.
I understand that in Linux environment is possible online trace level
changing.
Radiator started with "Trace 3" and after running "/etc/rc.d/rc.radiator
inc" I have in log file only:
Fri Aug 6 10:27:55 2010 648930: INFO: Trace level changed to 4
Fri Aug 6 10:
10 matches
Mail list logo
