[tkined] Problem handling engineId on the tcl interface in scotty 3.0.0

Peder Chr. Norgaard (pcn@tbit.dk)
Sun, 7 Mar 1999 23:44:33 +0100 (MET)

Hello.
You may already be aware of this problem - then again you may not.

SNMP Engine IDs are, according to RFC 2271, octet strings that are
"binary" in nature, i.e., they are usually not printable. Scotty 3.0.0
beta (I use the version from November 4th 1998) seems to treat the
"engineID" session option as a printable text - and this does not work
very well when scotty discovers an engine when an unprintable id. Scotty
discovers and uses the the engine id correctly, but if you use the
"<session> configure" or "<session> cget engineID" you don't get what you
expect.

best regards

--peder chr.


Peder Chr. Nørgaard System Developer, M. Sc.
Telebit Communications A/S tel: +45 86 28 81 77 - 49
Fabrikvej 11 fax: +45 86 28 81 86
DK-8260 Viby J Denmark e-mail: pcn@tbit.dk

--
!! 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.