What I did was change rfc1759 so the OCTET STRING field I wanted to read
was DisplayString in the mib we used...
I've seen behavior in some other managers which I really don't
understand (I think its doing scanning of the strings...if all bytes
pass isprint() and it ends in a NULL, it treats it as an ascii string,
Otherwise its displays hex bytes...
I understand DisplayString is
deprecated, and Utf8String should be used in future mibs...
>
> >>>>> Marty Leisner writes:
>
> Marty> I hacked up the mib definition and defined these to be
> Marty> DisplayString's.
>
> Marty> But the asciiz structure seems to be inferred (DisplayString is
> Marty> just OctetString).
>
> I am not sure I understand the last comment. Note, the DisplayString
> definition in RFC 1903 has a DISPLAY-HINT clause which clearly says
> that each byte should be treated as ASCII. Scotty interprets these
> DISPLAY-STRINGs and hence there is a big difference.
> Juergen
> --
> Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw
> Technical University Braunschweig, Dept. Operating Systems & Computer Networks
> Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)
-- marty leisner@sdsp.mc.xerox.com The Feynman problem solving Algorithm 1) Write down the problem 2) Think real hard 3) Write down the answer Murray Gell-mann in the NY Times
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.