[Net-snmp-patches] [ net-snmp-Feature Requests-573267 ] Comply with RFC1213 for Linux.

[<no...@so...>]

Feature Requests item #573267, was opened at 2002-06-24 20:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=362694&aid=573267&group_id=12694

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Comply with RFC1213 for Linux.

Initial Comment:
This may be considered an enhancement request.

To comply with RFC1213, at least the following changes
would need to be done:

agent/mibgroup/mibII/interfaces.c should be changed
from:
#ifdef WIN32
    {IFADMINSTATUS, ASN_INTEGER, RWRITE, var_ifEntry,
3, {2, 1, 7}},
#else
    {IFADMINSTATUS, ASN_INTEGER, RONLY, var_ifEntry, 3,
{2, 1, 7}},
#endif

to at least:

#ifdef WIN32
    {IFADMINSTATUS, ASN_INTEGER, RWRITE, var_ifEntry,
3, {2, 1, 7}},
#ifdef LINUX
    {IFADMINSTATUS, ASN_INTEGER, RWRITE, var_ifEntry,
3, {2, 1, 7}},
#else
    {IFADMINSTATUS, ASN_INTEGER, RONLY, var_ifEntry, 3,
{2, 1, 7}},
#endif

or probably better remove the #ifdef WIN32 and make all
architectures have:

{IFADMINSTATUS, ASN_INTEGER, RWRITE, var_ifEntry, 3,
{2, 1, 7}},


agent/mibgroup/mibII/ip.c should be changed from:

#ifdef WIN32
    {IPFORWARDING, ASN_INTEGER, RWRITE, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RWRITE, var_ip, 1, {2
}},
#else
    {IPFORWARDING, ASN_INTEGER, RONLY, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RONLY, var_ip, 1, {2
}},
#endif

to at least:

#ifdef WIN32
    {IPFORWARDING, ASN_INTEGER, RWRITE, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RWRITE, var_ip, 1, {2
}},
#ifdef LINUX
    {IPFORWARDING, ASN_INTEGER, RWRITE, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RWRITE, var_ip, 1, {2
}},
#else
    {IPFORWARDING, ASN_INTEGER, RONLY, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RONLY, var_ip, 1, {2
}},
#endif

or probably better remove the #ifdef WIN32 and make all
architecture have:

    {IPFORWARDING, ASN_INTEGER, RWRITE, var_ip, 1, {1
}},
    {IPDEFAULTTTL, ASN_INTEGER, RWRITE, var_ip, 1, {2
}},


There may be RFC1213 differences that I'm not including
since I have not done a complete evaluation.

Thank you.



----------------------------------------------------------------------

>Comment By: Dave Shield (dts12)
Date: 2002-06-25 16:23

Message:
Logged In: YES 
user_id=88893

There's very little point in just changing the MIB
registration entries.
That's not going to magically make these objects writeable.
The hard part is in providing the code to implement the SET
handling in each case.   If you are able to provide such a
patch,
we would be delighted to incorporate it.

Also note that the access settings in RFC 1213 (and elesewhere)
are the *maximum* access - not minimum.  It is perfectly
valid to
implement a Read-Write object as Read-Only,.

Dave

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=362694&aid=573267&group_id=12694