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

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-2997495 ] V5.4, V5.5, trunk,
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2010-05-06 8:13:43
Message-ID: E1O9wDH-0003g7-RW () sfs-web-7 ! v29 ! ch3 ! sourceforge ! com
[Download RAW message or body]

Bugs item #2997495, was opened at 2010-05-06 10:13
Message generated for change (Tracker Item Submitted) made by bvassche
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=2997495&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: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By:  (bvassche)
Assigned to: Nobody/Anonymous (nobody)
Summary: V5.4, V5.5, trunk, Cygwin: tcpConnTable info incorrect

Initial Comment:
Start snmpd as follows:
$ agent/snmpd.exe -f -Lo

Run the following command from another shell:
$ snmpwalk -v2c -cpublic localhost tcpConnState|grep '0\.0\.0\.0'
TCP-MIB::tcpConnState.0.0.0.0.135.0.0.0.0.8397 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.161.0.0.0.0.20694 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.199.0.0.0.0.24635 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.445.0.0.0.0.26683 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.705.0.0.0.0.12516 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.912.0.0.0.0.39016 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.1234.0.0.0.0.26798 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.2222.0.0.0.0.45144 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.8000.0.0.0.0.53291 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.9001.0.0.0.0.51317 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.12915.0.0.0.0.57529 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.16992.0.0.0.0.4216 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.16993.0.0.0.0.14548 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.20011.0.0.0.0.16593 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.20012.0.0.0.0.24771 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.37493.0.0.0.0.30945 = INTEGER: listen(2)
TCP-MIB::tcpConnState.0.0.0.0.44444.0.0.0.0.61458 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.1058.0.0.0.0.28811 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.1090.0.0.0.0.47300 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.2391.0.0.0.0.6329 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.8888.0.0.0.0.2077 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.11018.0.0.0.0.63601 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.12434.0.0.0.0.45211 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.15289.0.0.0.0.26765 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.15751.0.0.0.0.63655 = INTEGER: listen(2)
TCP-MIB::tcpConnState.127.0.0.1.32000.0.0.0.0.22724 = INTEGER: listen(2)
TCP-MIB::tcpConnState.192.168.1.102.139.0.0.0.0.39054 = INTEGER: listen(2)
TCP-MIB::tcpConnState.192.168.106.1.139.0.0.0.0.221 = INTEGER: listen(2)
TCP-MIB::tcpConnState.192.168.231.1.139.0.0.0.0.28794 = INTEGER: listen(2)

This information doesn't match the netstat output: the last component of the index \
should be zero but it isn't.

Netstat output:

$ netstat -an|grep 'TCP.*0\.0\.0\.0:'
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:161            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:199            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:705            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:912            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1234           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2222           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8000           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:9001           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:12915          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:16992          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:16993          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:20011          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:20012          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:37493          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:44444          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1058         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1090         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:2391         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:8888         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:11018        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:12434        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:15289        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:15751        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:32000        0.0.0.0:0              LISTENING
  TCP    192.168.1.102:139      0.0.0.0:0              LISTENING
  TCP    192.168.106.1:139      0.0.0.0:0              LISTENING
  TCP    192.168.231.1:139      0.0.0.0:0              LISTENING


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

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

------------------------------------------------------------------------------
_______________________________________________
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] 

Configure | About | News | Add a list | Sponsored by KoreLogic