ARM (debian linux) with net-snmp 5.0.9
get existing data:
snmp0 walk res ipRouteDest {puts stderr $res}
{1.3.6.1.2.1.4.21.1.1.0.0.0.0 IpAddress 0.0.0.0}
{1.3.6.1.2.1.4.21.1.1.192.168.0.0 IpAddress 192.168.0.0}
{1.3.6.1.2.1.4.21.1.1.224.0.0.0 IpAddress 224.0.0.0}
write existing data back causes segmentation fault:
snmp0 set {{1.3.6.1.2.1.4.21.1.1.192.168.0.0 IpAddress 192.168.0.0}}
additional trying to write iilegal types Counter32/Integer32/TimeTicks/Unsigned32 returns noSuchName instead of WrongType error.
snmp0 set {1.3.6.1.2.1.4.21.1.1.0.0.0.0 Counter32 1}
noSuchName 0 {1.3.6.1.2.1.4.21.1.1.192.168.0.0 IpAddress 192.168.0.0}
a tcl/scotty script was used for automated agent testing and it found more than the 4 bugs submitted today.
if anyone is interested to get it, contact stefan.g.r.finzel AT t-online.de
Logged In: YES
user_id=848638
Originator: NO
The Net-SNMP version you're using is quite old. The 5.0.x and 5.1.x branches have already been declared end-of-life and won't receive any further development or bug fixes (except for major security issues).
Please retest with current code (see http://www.net-snmp.org/dev/schedule.html and http://www.net-snmp.org/download.html\) and report back.
Logged In: YES
user_id=88893
Originator: NO
I have confirmed that all currently active lines
do *not* crash in the circumstances described,
and *do* return WrongType on an invalid SET.
The current code doesn't actually handle SET requests
for ipRouteDest correctly - requiring that the type
is Octet String rather than IP Address.
Now fixed.