[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-1685131 ] write_rte causes segmentation fault
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2007-03-25 19:07:20
Message-ID: E1HVY3k-0001bV-0d () sc8-sf-web21 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1685131, was opened at 2007-03-21 12:33
Message generated for change (Comment added) made by dts12
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1685131&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: agent
Group: embedded
> Status: Closed
> Resolution: Invalid
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: write_rte causes segmentation fault

Initial Comment:
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


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

> Comment By: Dave Shield (dts12)
Date: 2007-03-25 20:07

Message:
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.

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

Comment By: Thomas Anders (tanders)
Date: 2007-03-23 13:14

Message:
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.

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

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

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-bugs mailing list
Net-snmp-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-bugs


[prev in list] [next in list] [prev in thread] [next in thread]