Hi Jason, Basically you set up a separate <Client> clause for each NAS, and set NasType as appropriate for each NAS (if you want sim-use double checking) The Dictionary you use will depend on the exact mix of NASs you are using. I would recommend you start with the standard dictionary (called "dictionary"), and then alter it to add extra items if it proves necessary (ie if Radiator complains about attributes missing from your dictionary). Hope that helps. Cheers. PS, Ascend are currently moving toward using vendor-sepecif attributes instead of the commadeered IETF attributes they used to use. If you have a NAS that is using the new attributes, we have a new dictionary that understands them. ---------------------------------------------------------------------------- --------------- Mike McCauley [EMAIL PROTECTED] Open System Consultants +61 3 9598 0985 Mike is travelling right now, and there may be delays in our correspondence. -----Original Message----- From: Jason J. Horton <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Wednesday, April 07, 1999 6:40 AM Subject: (RADIATOR) Using multiple NASs >How does Radiator handle multiple NAS types? >Do I have to use separate dictionary files, or >do I have to chunk together multiple dictionary >files into one huge one? Also, can I use the same users >file unmodified(specifically a merit radius users file) > >Am Interested in supporting an Ascend MAX and Lucent PM2e's > > -Jason J. Horton <[EMAIL PROTECTED]> > Senior Network & Systems Engineer > Intercom Online Inc. > 212.378.2202 | http://www.intercom.com > > >=== >To unsubscribe, email '[EMAIL PROTECTED]' with >'unsubscribe radiator' in the body of the message. > === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
