ports/54551: snmpd returns bad MIB variable value: tcp.tcpCurrEstab.0

Mário Freitas sub_0 at netcabo.pt
Wed Jul 16 18:40:17 UTC 2003


>Number:         54551
>Category:       ports
>Synopsis:       snmpd returns bad MIB variable value: tcp.tcpCurrEstab.0
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 16 11:40:15 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Mário Freitas
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
System: FreeBSD x.xpto.org 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Mon Jul 14 02:02:49 WEST 2003 sub_0 at x.xpto.org:/usr/obj/usr/src/sys/XPTO i386


	
>Description:
It seems that ucd snmpd versions 4.2.6 and 5.0.8 (at least) are having problems when
snmpgetting the MIB variable tcp.tcpCurrEstab.0 which is always the same
(tcp.tcpCurrEstab.0 = Gauge32: 0) wether you have established tcp connections or not.
I've analized this problem and I'm sure the problem is in the port, not in the kernel.

>How-To-Repeat:
Just establish some tcp connection and snmpget that variable and you will see it is
always 0(zero).
>Fix:

	


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list