Your message dated Sun, 28 Aug 2005 16:14:47 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322518: portnumber-bug in tcpdump 3.8.3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Aug 2005 06:23:38 +0000
>From [EMAIL PROTECTED] Wed Aug 10 23:23:38 2005
Return-path: <[EMAIL PROTECTED]>
Received: from betula.xs4all.nl (persijn.net) [213.84.222.44]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E36Ta-0007MY-00; Wed, 10 Aug 2005 23:23:38 -0700
Received: from www.persijn.net (debian [127.0.0.1])
by persijn.net (Postfix) with SMTP id B9546177F7
for <[EMAIL PROTECTED]>; Thu, 11 Aug 2005 08:23:30 +0200 (CEST)
Received: from 145.7.71.82
(SquirrelMail authenticated user arie)
by www.persijn.net with HTTP;
Thu, 11 Aug 2005 08:23:30 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 11 Aug 2005 08:23:30 +0200 (CEST)
Subject: portnumber-bug in tcpdump 3.8.3
From: "Arie Kraai" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary="----=_20050811082330_93785"
X-Priority: 3
Importance: Normal
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.8 required=4.0 tests=BAYES_01,HAS_PACKAGE,
PRIORITY_NO_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
------=_20050811082330_93785
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Package: tcpdump
Version: 3.8.3-5
tcpdumps of NFS-over-TCP sessions gave funny portnumbers like this:
15:34:09.718521 IP 172.27.20.180.2049 > 145.7.10.224.2726518068
The very same tcpdump-logfile (attached to this bugreport) gave correct
output when read by ethereal:
Transmission Control Protocol, Src Port: 2049 (2049), Dst Port: 798 (798)=
,
Seq: 116, Ack: 228, Len: 124
... and reveals the funny "portnumber" as the XID-value:
Remote Procedure Call, Type:Reply XID:0xa2835d34
Fragment header: Last fragment, 120 bytes
XID: 0xa2835d34 (2726518068)
The (correctly working) version of libpcap is 0.8.3
Tcpdump itself is 3.8.3-5 (currently *the* tcpdump in stable)
Kernelversion or other software-versions are not relevant in this case
Can you have this non-critical, but somewhat annoying tcpdump-bug fixed?
Thank you very much, Arie Kraai
------=_20050811082330_93785
Content-Type: application/octet-stream; name="tcpdumpp-bug"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="tcpdumpp-bug"
1MOyoQIABAAAAAAAAAAAAP//AAABAAAAUQL6Qp6OCgCyAAAAsgAAAAAFXsbg0ADAT4pnfAgARQAA
pLNdQAA/BitAkQcK4KwbFLQDHggBQE013ZeHu3CAGAW02dwAAAEBCAoAL38iFjdEw4AAAGyhg100
AAAAAAAAAAIAAYajAAAAAwAAAAEAAAABAAAAIAAADCgAAAAFa3JhYWkAAAAAAAAAAAAAAAAAAAEA
AAAAAAAAAAAAAAAAAAAgQAEAAf////8ACgAAAAABbAAAADgACgAAAAABbAAAADhRAvpCwLkKALYA
AAC2AAAAAMBPimd8AKCOeN3vCABFAACo8kFAAD0G7lesGxS0kQcK4AgBAx6Xh7twQE02TYAYgACc
KAAAAQEIChY3ZgYAL38igAAAcKGDXTQAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAB7QAA
AAIAAAd/AAAHfwAAAAAAAABgAAAAAAAAAAAAAAAAAAAAAAAAAABAAQABAAAAAAAAAWxC+f4NBajl
+ELBA0QAAAAAQt2ESTC18LBRAvpCnboKAEIAAABCAAAAAAVexuDQAMBPimd8CABFAAA0s19AAD8G
K66RBwrgrBsUtAMeCAFATTZNl4e75IAQBbRDkwAAAQEICgAvfy0WN2YGUQL6QjDCCgC2AAAAtgAA
AAAFXsbg0ADAT4pnfAgARQAAqLNhQAA/Bis4kQcK4KwbFLQDHggBQE02TZeHu+SAGAW0tn4AAAEB
CAoAL38vFjdmBoAAAHCig100AAAAAAAAAAIAAYajAAAAAwAAAAQAAAABAAAAIAAADCgAAAAFa3Jh
YWkAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAgQAEAAf////8ACgAAAAABbAAAADgACgAA
AAABbAAAADgAAAAfUQL6Qrn2CgC+AAAAvgAAAADAT4pnfACgjnjd7wgARQAAsPJFQAA9Bu5LrBsU
tJEHCuAIAQMel4e75EBNNsGAGIAAmgIAAAEBCAoWN2YHAC9/L4AAAHiig100AAAAAQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAQAAAAIAAAHtAAAAAgAAB38AAAd/AAAAAAAAAGAAAAAAAAAAAAAAAAAA
AAAAAAAAAEABAAEAAAAAAAABbEL5/g0FqOX4QsEDRAAAAABC3YRJMLXwsAAAAB9RAvpChZILAEIA
AABCAAAAAAVexuDQAMBPimd8CABFAAA0s2NAAD8GK6qRBwrgrBsUtAMeCAFATTbBl4e8YIAQBbRC
agAAAQEICgAvf2UWN2YH
------=_20050811082330_93785--
---------------------------------------
Received: (at 322518-done) by bugs.debian.org; 28 Aug 2005 14:14:16 +0000
>From [EMAIL PROTECTED] Sun Aug 28 07:14:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from yeast.orebokech.com [82.67.41.165] (romain)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E9NvM-0007tF-00; Sun, 28 Aug 2005 07:14:16 -0700
Received: from pacem.orebokech.com (pacem.orebokech.com [192.168.1.3])
by yeast.orebokech.com (Postfix) with ESMTP id E0B7C12F83;
Sun, 28 Aug 2005 16:14:14 +0200 (CEST)
Received: by pacem.orebokech.com (Postfix, from userid 1000)
id 2FF515239A; Sun, 28 Aug 2005 16:14:47 +0200 (CEST)
From: Romain Francoise <[EMAIL PROTECTED]>
To: "Arie Kraai" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#322518: portnumber-bug in tcpdump 3.8.3
Organization: The Debian Project
References: <[EMAIL PROTECTED]>
Date: Sun, 28 Aug 2005 16:14:47 +0200
In-Reply-To: <[EMAIL PROTECTED]> (Arie
Kraai's message of "Thu, 11 Aug 2005 08:23:30 +0200 (CEST)")
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
"Arie Kraai" <[EMAIL PROTECTED]> writes:
> tcpdumps of NFS-over-TCP sessions gave funny portnumbers like this:
> 15:34:09.718521 IP 172.27.20.180.2049 > 145.7.10.224.2726518068
That's not a bug, but a feature. Instead of the (fixed) TCP port, it
shows you the RPC XID, as documented in the man page.
If you _really_ want to see the TCP port, use the -q option.
Cheers,
--
,''`.
: :' : Romain Francoise <[EMAIL PROTECTED]>
`. `' http://people.debian.org/~rfrancoise/
`-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
