netbsd-bugs@netbsd.org
[Top] [All Lists]

bin/39310: netstat command will show server-sockets without -a option

Subject: bin/39310: netstat command will show server-sockets without -a option
From:
Date: Thu, 07 Aug 2008 11:35:13 UTC
Newsgroups: fa.netbsd.bugs

>Number:         39310
>Category:       bin
>Synopsis:       netstat command will show server-sockets without -a option
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 07 11:35:00 +0000 2008
>Originator:     Wolfgang Stukenbrock
>Release:        NetBSD 4.0_STABLE
>Organization:
Dr. Nagler & Company GmbH
        
>Environment:
        
        
System: NetBSD s102 4.0_STABLE NetBSD 4.0_STABLE (NSW-S102) #3: Tue Jul 22 
12:58:04 CEST 2008 
wgstuken@s012:/export/NetBSD-4.0/N+C-build/.OBJDIR_i386/export/NetBSD-4.0/src/sys/arch/i386/compile/NSW-S102
 i386
Architecture: i386
Machine: i386
>Description:
        The command netstat should not report "server"-Sockets in state LISTEN 
by default,
        but in 4.0_STABLE it will do so - sorry no real 4.0 machine available 
for cross-check,
        but I assume the bug is there too.
        example: "netstat -n | grep tcp | head -20
tcp        0      0  127.0.0.1.682          127.0.0.1.111          TIME_WAIT
tcp        0      0  127.0.0.1.681          127.0.0.1.1021         TIME_WAIT
tcp        0      2  172.20.0.2.513         212.222.97.70.797      ESTABLISHED
tcp        0      0  172.20.0.2.687         172.19.0.2.2049        ESTABLISHED
tcp        0      0  172.20.0.2.690         172.17.1.1.2049        ESTABLISHED
tcp        0      0  172.20.0.2.693         212.222.197.145.2049   ESTABLISHED
tcp        0      0  172.20.0.2.696         212.222.97.161.2049    ESTABLISHED
tcp        0      0  172.20.0.2.513         212.222.97.70.798      ESTABLISHED
tcp        0      0  172.20.0.2.143         62.220.15.190.51247    ESTABLISHED
tcp        0      0  172.20.0.2.707         212.222.97.130.2049    ESTABLISHED
tcp        0      0  172.20.0.2.143         62.220.15.190.51293    ESTABLISHED
tcp        0      0  172.20.0.2.139         172.20.0.154.1590      ESTABLISHED
tcp        0      0  172.20.0.2.513         212.222.97.70.803      ESTABLISHED
tcp        0      0  172.20.0.2.139         172.20.0.51.1100       ESTABLISHED
tcp        0      0  *.139                  *.*                    LISTEN
tcp        0      0  *.445                  *.*                    LISTEN
tcp        0      0  172.20.0.2.1712        *.*                    LISTEN
tcp        0      0  172.20.0.2.22          212.222.97.98.2622     ESTABLISHED
tcp        0      0  172.20.0.2.2049        172.17.0.3.770         ESTABLISHED
tcp        0      0  172.20.0.2.22          212.222.97.101.60171   ESTABLISHED

        The two lines with "*.139" and "*.445" should not be there.
        Placing the output of "netstat -n" and "netstat -an" into two files and 
diff then
        will report
1c1
< Active Internet connections
---
> Active Internet connections (including servers)
82c82
< Active Internet6 connections
---
> Active Internet6 connections (including servers)

        It looks like the check for the wildcard address rails for some reasons.
>How-To-Repeat:
        run e.g. "netstat -n | grep tcp" on a machine.
>Fix:
        not known - no further analyses done for now

>Unformatted:
        
        

<Prev in Thread] Current Thread [Next in Thread>