Mark> I'm having a problem using the BITS syntax with scotty
Mark> (version 2.1.7).
Mark> I believe a varBind with a syntax of BITS is supposed to be
Mark> encoded as an OCTET STRING(4) on the wire, per sxn 8.3 of RFC
Mark> 1906. What I'm seeing with scotty is a syntax of NULL(5), and
Mark> a value length of 0.
You are right. BITS seem to be broken. They should be mapped to an
OCTET STRING, but I never really tested it.
Mark> I've noticed in tnmSnmpSend.c scotty source file, at line 862
Mark> case ASN1_BIT_STRING:
Mark> packet = Tnm_BerEncNull(packet, packetlen, ASN1_NULL);
Mark> break;
The ASN1_BIT_STRING stuff is from the old party days. This needs to be
removed.
Mark> My question is this: Is this a known scotty issue that is on a
Mark> list for a fix in a future release? Or, am I misunderstanding
Mark> how the BITS syntax is supposed to work?
You are perfectly fine. I will check if I can come up with a fix.
Your detailed report is really helpful.
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 3283)-- !! 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.