Hi Jose -
Right - understood.
In this case I would probably use separate Radiator processes as intermediates
between your main server and the targets that require special AVpair processing.
You would forward the original request unchanged and then deal with whatever
changes are required on
Hi,
I have somthing similar to this:
Handler Client-Identifier=PGW, Acct-Status-Type=Start
Identifier PGW_START
AccountingHandled
AuthBy GROUP
AuthByPolicy ContinueUntilReject
AuthBy RADIUS
Host
Hi again -
You could also use an AuthBy MULTICAST clause instead of multiple AuthBy RADIUS
clauses.
regards
Hugh
On 25 Apr 2015, at 09:41, Hugh Irvine h...@open.com.au wrote:
Hi Jose -
Right - understood.
In this case I would probably use separate Radiator processes as
Hello Jose -
One way to do this is with multiple Handler clauses and an AuthBy HANDLER
clause in the first one.
See the example in “goodies/authhandler.cfg”.
See also section 5.76 AuthBy HANDLER in the manual (“doc/ref.pdf”).
You can have a different PreAuthHook in each target Handler
Hi all,
I have a setup that forwards some accounting to several servers. I
need to mangle some attributes before a forward to the remote
server.One requirement is to have different mangling per host.
I couldn't found a way to change hook some code at AuthBy RADIUS, so I
implemented the attached
