HI,
Dave't answers below are right on target. One other consideration is the interoperability with managers. Some poorly designed managers make assumptions about community string values, such as ONLY ASCII letters and digits (no spaces or punctuation characters). Also, some agents also have the same restrictions because they save their configuration in ASCII text files and the parsers for the files cannot cope with community string values that are not just ASCII letters and digits. So, testing on one system (manager or agent) is not applicable to all. Sad situation. And remember, a community string value is NOT a password. On Mon, 1 Nov 2004, Dave Shield wrote: > > > I would also like to know whether community string can be unicode > > or is it only ASCII? > > The same answer applies: > > > > Nothing inherent in SNMP, no. > > Assorted MIB tables make various assumptions > > DisplayString is defined as being ASCII only. > SnmpAdminString can take UTF values. > So if you used a non-ASCII community string, > this would break any MIB expecting a DisplayString value. > > > But the SNMP protocol itself should work fine. > (Note - *should* - suck it and see!) > > Dave Regards, /david t. perkins ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
