bin/105334: Error in output of tcpdump(1)

[Oliver Fromme]

antoine at 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.'