From owner-freebsd-bugs@FreeBSD.ORG Mon Apr 7 19:24:14 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE7201065674; Mon, 7 Apr 2008 19:24:14 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 316478FC16; Mon, 7 Apr 2008 19:24:13 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m37JOA3u051445; Mon, 7 Apr 2008 21:24:12 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m37JOAXe051443; Mon, 7 Apr 2008 21:24:10 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <200804071924.m37JOAXe051443@lurza.secnetix.de> To: antoine@FreeBSD.org Date: Mon, 7 Apr 2008 21:24:10 +0200 (CEST) In-Reply-To: <200804071844.m37IiOlF090439@freefall.freebsd.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 07 Apr 2008 21:24:12 +0200 (CEST) Cc: olli@secnetix.de, freebsd-bugs@FreeBSD.org Subject: Re: bin/105334: Error in output of tcpdump(1) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2008 19:24:14 -0000 antoine@FreeBSD.org wrote: > > Synopsis: Error in output of tcpdump(1) > > State-Changed-From-To: open->feedback > State-Changed-By: antoine > State-Changed-When: Mon Apr 7 18:35:23 UTC 2008 > State-Changed-Why: > > From the tcpdump man page: > %%% > Sun NFS (Network File System) requests and replies are printed as: > src.xid > dst.nfs: len op args > src.nfs > dst.xid: reply stat len op results > [...] > %%% > > So what you see is the transaction id and not a source port. > If you want to see the port you can use tcpdump -q. > Do you agree that this PR can be closed? Well, yes, close it. I still think that tcpdump behaviour is wrong, or at least misleading. Having to specify -q (quiet?) to actually get more information (i.e. the port number, which I expect to be displayed by _default_) is not intuitive, and it's not documented this way. This makes it more difficult to post-process output in scripts. But all of that is probably way beyond the scope of this PR, so please close it. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.'