Hello Tim -
In a trace 4 debug, Radiator only shows the attributes that it understands from the dictionary file (by definition). If you want to identifiy undefined attributes, you should run trace 5 and decode the hex dumps. BTW - the debug output should tell you what attribute number it can't find in the dictionary. Note that there are *lots* of new attribute definitions in Radiator 3.1. regards Hugh On Tue, 28 May 2002 01:12, Timothy G. Wells wrote: > Greetings, > > When putting radiator into debug mode (v 2.18) does it show, in the details > file, all the attributes or just the ones radiator knows from the > dictionary? I'm trying to see what else is being sent to me. > > Thanks, > > -- Tim > > === > 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. -- 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.
