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

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-1679532 ] agent returns 0 for process id in tcp and
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2009-01-14 16:52:23
Message-ID: E1LN8yd-0005VR-Ce () h45xhf1 ! ch3 ! sourceforge ! com
[Download RAW message or body]

Bugs item #1679532, was opened at 2007-03-13 03:56
Message generated for change (Settings changed) made by dts12
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=1679532&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: None
Group: None
> Status: Closed
> Resolution: Fixed
Priority: 5
Private: No
Submitted By: Varun_C (c_varun)
Assigned to: Nobody/Anonymous (nobody)
Summary: agent returns 0 for process id in tcp and udp mib

Initial Comment:
uname: Linux 2.6.18.2-34-default
Distribution: OpenSUSE 10.2
NET-SNMP version: 5.5.dev (CVS 2007/Feb/23)
configuration: --enable-ipv6

Problem Description:

The object tcpConnectionProcess and tcpListenerProcess
of tcp-mib seems to return 0 by default instead of process id as described in RFC \
4022.

The object udpEndpointProcess of udp-mib seems to
return 0 by default instead of process id as described in RFC 4113.

Commands to reproduce the problem

#snmpwalk -v 2c -c public localhost .1.3.6.1.2.1.6.19
TCP-MIB::tcpConnectionProcess.ipv4."9.124.35.24".2965.ipv4."9.184.220.24".1352 = \
Gauge32: 0 TCP-MIB::tcpConnectionProcess.ipv4."9.124.35.24".6533.ipv4."9.5.251.43".6667 \
= Gauge32: 0 TCP-MIB::tcpConnectionProcess.ipv4."9.124.35.24".8207.ipv4."9.37.253.145".143 \
= Gauge32: 0 TCP-MIB::tcpConnectionProcess.ipv4."9.124.35.24".24553.ipv4."9.184.220.24".1352 \
= Gauge32: 0 TCP-MIB::tcpConnectionProcess.ipv4."9.124.35.24".28785.ipv4."9.37.253.145".143 \
= Gauge32: 0 TCP-MIB::tcpConnectionProcess.ipv6."00:00:00:00:00:00:00:00:00:00:ff:ff:09:7c:23:18".21554.ipv6."00:00:00:00:00:00:00:00:00:00:ff:ff:09:11:88:4c".1533 \
= Gauge32: 0

#snmpwalk -v 2c -c public localhost .1.3.6.1.2.1.6.20
TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".111 = Gauge32: 0
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".25 = Gauge32: 0
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".631 = Gauge32: 0
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".8979 = Gauge32: 0
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".10555 = Gauge32: 0
TCP-MIB::tcpListenerProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00".22 \
= Gauge32: 0 TCP-MIB::tcpListenerProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00".56869 \
= Gauge32: 0 TCP-MIB::tcpListenerProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01".25 \
= Gauge32: 0 TCP-MIB::tcpListenerProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01".631 \
= Gauge32: 0

#snmpwalk -v 2c -c public localhost .1.3.6.1.2.1.7.7
UDP-MIB::udpEndpointProcess.ipv4."0.0.0.0".68.unknown."".0.0 = Gauge32: 0
UDP-MIB::udpEndpointProcess.ipv4."0.0.0.0".111.unknown."".0.0 = Gauge32: 0
UDP-MIB::udpEndpointProcess.ipv4."0.0.0.0".161.unknown."".0.0 = Gauge32: 0
UDP-MIB::udpEndpointProcess.ipv4."0.0.0.0".631.unknown."".0.0 = Gauge32: 0
UDP-MIB::udpEndpointProcess.ipv4."0.0.0.0".1076.unknown."".0.0 = Gauge32: 0
UDP-MIB::udpEndpointProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00".161.unknown."".0.0 \
= Gauge32: 0 UDP-MIB::udpEndpointProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00".1026.unknown."".0.0 \
= Gauge32: 0 UDP-MIB::udpEndpointProcess.ipv6."00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00".20830.unknown."".0.0 \
= Gauge32: 0


In all the above cases the return value is always 0, instead of pid.

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

> Comment By: Dave Shield (dts12)
Date: 2009-01-14 16:52

Message:
Patch #1670511 applied  (SVN revision 16319)

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

Comment By: Varun_C (c_varun)
Date: 2007-03-13 03:58

Message:
Logged In: YES 
user_id=1725940
Originator: YES

I have a proposed patch for the above problem. This is a set of patches
with Request ID#1670511
https://sourceforge.net/tracker/index.php?func=detail&aid=1670511&group_id=12694&atid=312694


Thankyou.

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

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

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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]