Actually, it does not parse with scotty 2.1.8, either, but with
2.1.8 I have a work-around (details below). With 3.0.0 I have not even
been able to fix a work-around.
The problem (which I reported on this list in February 1998, at
which time the RFC was an Internet-draft) is in the parsing of what
tnm/snmp/tnmMibParser.c calls Node Lists, i.e. ASN.1 object identifiers
that are sligthly more complex than usual:
atmTCMIB MODULE-IDENTITY .... ::= { mib-2 37 3 }
and
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
With scotty 2.1.8 I succeeded in parsing this by modifying the TC
MIB slightly:
atmTCMIB MODULE-IDENTITY .... ::= { mib-2 atmMIB(37) 3 }
and
atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 atmMIB(37) atmMIBObjects(1) 1}
(the symbolic values taken from RFC 2515).
With scotty 3.0.0 I have not been able to figure out a similar
work-around.
Any help will be appreciated, whether a work-around or a solution
in the parser.
best regards
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.