> From: [email protected] [mailto:[email protected]]
> Sent: Sunday, July 05, 2009 9:24 AM
> p...@nani:~$ snmpset -v 2c -c public localhost ip.ipForwarding.0 i 2
> Error in packet.
> Reason: notWritable (That object does not support modification)
>
> If this not allowed how should i get the information about
> thee objects which
> supports read and write.
> I am very much confused by this behavior ( R/W objects not
> allowing SET
> operations ).
The definition in the MIB says that this object may be written, but the
implementation you have available does not support writes of that object. Note
the definition:
[SNIP]
ipForwarding OBJECT-TYPE
SYNTAX INTEGER {
forwarding(1), -- acting as a router
notForwarding(2) -- NOT acting as a router
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The indication of whether this entity is acting as an IPv4
router in respect to the forwarding of datagrams received
by, but not addressed to, this entity. IPv4 routers forward
datagrams. IPv4 hosts do not (except those source-routed
via the host).
When this object is written, the entity should save the
change to non-volatile storage and restore the object from
non-volatile storage upon re-initialization of the system.
Note: a stronger requirement is not used because this object
was previously defined."
::= { ip 1 }
[/SNIP]
The key is the MAX-ACCESS definition. This implies that there may be
less access available, either due to security restrictions, the MIB not being
available on a given host, or, as in your case, the MIB implementation not
supporting writes. If you wish to manage the host forwarding ability via SNMP,
you will first need to either find or write an implementation that can do so.
HTH,
Mike
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
