Hello Jonathon -
My usual approach in this situation is to use Handlers, together with the Class attribute.
Something like this:
# define AuthBy clauses
<AuthBy ...>
Identifier CheckWhatever
.....
AddToReply Class = CheckWhatever
</AuthBy>
<AuthBy .....>
Identifier CheckSomethingElse
.....
AddToReply Class = CheckSomethingElse
</AuthBy>
.....
# define Handlers
<Handler Request-Type = Accounting-Request, Class = CheckWhatever>
AuthBy CheckWhatever
.....
</Handler>
<Handler Request-Type = Accounting-Request, Class = CheckSomethingElse>
AuthBy CheckSomethingElse
.....
</Handler>
.....
<Handler>
AuthByPolicy ContinueUntilAccept
AuthBy CheckWhatever
AuthBy CheckSomethingElse
....
</Handler>
regards
Hugh
On Friday, Dec 27, 2002, at 07:50 Australia/Melbourne, mail.baysat.net wrote:
Hi,
��� I am currently using radiator as a central authentication server for numerous wireless hotspots and dialup networks.� Each hotspot can authenticate users�from multiple networks so I have a series of AuthBy clauses for each Handler.� I need to keep track of what AuthBy clauses each user was authenticated by so I can get the accounting packets to the correct authentication server.� I am currently doing this by passing a value in a radius attribute that I check for in accounting handlers that supercede the authentication handlers.
I was hoping there would be a cleaner way of doing this.� I had though I may be able to use the session ID and the session database somehow but am not sure where to start.� Do you have any suggestions on this?
�
Thanks
Jonathon Lindbo
�
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
