> > Another question I have is using Auth-By in a users file. For example: > > > > <Handler NAS-IP-Address = 1.2.3.4> > > <AuthBy FILE> > > Filename nas-1.2.3.4 > > </AuthBy > > </Handler> > > > > nas-1.2.3.4: > > > > DEFAULT Calling-Station-Id = 111, Auth-Type = DoA > > > > DEFAULT Calling-Station-Id = 222, Auth-Type = DoB
Hello Hugh, I just realized something about my proposed config above, in that DoA and DoB will not get accounting. Basically 'DoA' and 'DoB' correspond to 2 different virtual ISPs and I need the accounting handled for each one differently, but in other words they need to GET the accounting. My guess is I need to write a new auth module that inherits AuthFILE. Looking at this I think I just need to add some code to call AuthGeneric::checkAttributes on an accounting request instead of just accepting it. Do you think that modification will work ok? Just FYI, the reason I am looking at the above type of configuration is I would like to reduce the number of handlers. We simply would have too many if we did this with all Handlers. The goal with the above config is to emulate a 'sub-handler' or cascading setup, where first the NAS IP is matched, then Calling-Station-Id only if NAS IP had matched. This will reduce the amount of processing for each packet. If you think there is some better way please let me know. Thanks, Viraj. === 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.