Hi all,

in our MIB we have the following definitions (only the important parts are
shown):

                UsnFunctionGroup ::= TEXTUAL-CONVENTION
                        STATUS current
                        DESCRIPTION
                                "xxx"
                        SYNTAX INTEGER
                                {
                                a(51),
                                b(53),
                                c(54),
                                d(55)
                                e(63),
                                f(64),
                                g(65),
                                h(70)
                                }


                setsCfgTmFunctionGroup OBJECT-TYPE
                        SYNTAX UsnFunctionGroup (54 | 65)
                        MAX-ACCESS read-write
                        STATUS current
                        DESCRIPTION
                                "blabla"
                        ::= { setsCfgTmEntry 4 }


the generated c code for this object ist:

    /** Check the ranges of the passed value for legality */
    if ( !(*val >= 54 && *val <= 54) || !(*val >= 65 && *val <= 65) )
    {
        return SNMP_ERR_WRONGVALUE;
    }

which yields an error for each of the two correct values 54 oder 65. The
'||' should be a '&&'.

If somebody could give me a hint where this has to be corrected in the mib2c
compiler I could submit a patch

thanks

Boris
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to