> I am having a problem with setting ip-forwarding with SNMP. That's probably because write support for this object hasn't been implemented on your particular architecture.
> When I try to set the object, I get this error: > snmpset -c <Name> 10.1.1.10 .1.3.6.1.2.1.4.1.0 i 1 > Error in packet. > Reason: (noSuchName) There is no such variable name in this MIB. > Failed object: IP-MIB::ipForwarding.0 If you tried with SNMPv2c or SNMPv3, you'd receive a slightly more informative error - probably 'notWritable' > Maybe this is a misunderstanding on my part, but since MAX-ACCESS is > read-write, snmp should allow me to write to this object, right?? The *maximum* access is read-write, so it's legitimate to attempt a SET request. But that doesn't mean that the agent necessarily implements write support (or that you'd automatically be authorised to set it). > Is this a bug? Not really. It's more of an unimplemented feature. If you wish to offer suitable code to tackle this, then we'd consider adding it to the code for future releases. Dave ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ 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
