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
tcpdumpp-bug
Description: Binary data
