Bug 466845

Summary: [PATCH] Change "unkn-4" to "probe0" in status of "netstat -o"
Product: Red Hat Enterprise Linux 5 Reporter: Masaki MAENO <maeno.masaki>
Component: net-toolsAssignee: Jiri Popelka <jpopelka>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: rvokal, ykopkova
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-16 09:27:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
net-tools package patch for probe0 timer working status none

Description Masaki MAENO 2008-10-14 05:45:28 UTC
Created attachment 320253 [details]
net-tools package patch for probe0 timer working status

Description of problem:
The display of "netstat -o" (on|off|keepalive|unkn-X) is not accurate. 
I think that "unkn-4" should be "probe0" that is working "probe0 timer 
(= ICSK_TIME_PROBE0 status = TCP Window Size is Zero) " in kernel.

Version-Release number of selected component (if applicable):
net-tools all version

How reproducible:
When TCP Window Size is zero (= network load is high), execute "netstat -o".
  
Actual results:
$ netstat -atno 
...
tcp        0      0 172.17.0.157:46124          172.19.0.2:22               ESTABLISHED keepalive (3871.19/0/0)
tcp        0      0 172.17.0.157:33733          172.17.0.156:445            ESTABLISHED off (0.00/0/0)
tcp        0      0 172.17.0.157:34300          172.20.128.2:22             ESTABLISHED unkn-4 (3871.19/0/0)
tcp        0      0 172.17.0.157:32903          172.20.128.2:22             ESTABLISHED keepalive (3871.19/0/0)
tcp        0      0 172.17.0.157:40209          172.19.0.2:143              ESTABLISHED off (0.00/0/0)
tcp        0      0 172.17.0.157:445            172.17.1.13:1029            ESTABLISHED keepalive (1342.25/0/0)
...

Expected results:
$ netstat -atno 
...
tcp        0      0 172.17.0.157:46124          172.19.0.2:22               ESTABLISHED keepalive (3871.19/0/0)
tcp        0      0 172.17.0.157:33733          172.17.0.156:445            ESTABLISHED off (0.00/0/0)
tcp        0      0 172.17.0.157:34300          172.20.128.2:22             ESTABLISHED probe0 (3871.19/0/0)
tcp        0      0 172.17.0.157:32903          172.20.128.2:22             ESTABLISHED keepalive (3871.19/0/0)
tcp        0      0 172.17.0.157:40209          172.19.0.2:143              ESTABLISHED off (0.00/0/0)
tcp        0      0 172.17.0.157:445            172.17.1.13:1029            ESTABLISHED keepalive (1342.25/0/0)
...

Comment 1 Zdenek Prikryl 2008-10-15 06:45:32 UTC
Seems reasonable, I'll use only "probe" instead of "probe0", because '0' could be confusing for other users.

Comment 2 Masaki MAENO 2008-10-15 07:01:08 UTC
OK. Please use "probe".

Comment 4 RHEL Program Management 2009-03-26 17:09:23 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 5 RHEL Program Management 2009-11-06 19:21:38 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 11 errata-xmlrpc 2009-12-16 09:27:06 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1677.html