Date: Thu, 9 Nov 2006 23:50:30 GMT From: Ricardo Nabinger Sanchez <rnsanchez@wait4.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/105334: Error in output of tcpdump Message-ID: <200611092350.kA9NoUbA002120@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/105334; it has been noted by GNATS.
From: Ricardo Nabinger Sanchez <rnsanchez@wait4.org>
To: Oliver Fromme <olli@lurza.secnetix.de>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: bin/105334: Error in output of tcpdump
Date: Thu, 9 Nov 2006 21:46:59 -0200
Hi Oliver,
On Thu, 9 Nov 2006 20:01:12 +0100 (CET)
Oliver Fromme <olli@lurza.secnetix.de> wrote:
> Now it gets even more interesting. I did what you suggested,
> then tried to view the file with "tcpdump -r" (on the same
> machine), and it displayed "0" for the port number in all
> places where the big 32bit numbers where displayed previously.
>
> Then I copied the file to a different machine (running an
> older FreeBSD 4.x), and tcpdump there displayed all of the
> port numbers correctly (i.e. neither big 32bit numbers nor
> zero). So it is definitely purely a display problem on my
> RELENG_6 machine. The contents of the capture file are OK.
I downloaded your files, tried with my tcpdump, yours, also with your
libpcap, and got consistent and uniform results, verified together with md5
after checking the output data.
There must be some odd problem somewhere on your libc. If you want to check
what's going on, you can recompile tcpdump enabling debug info (yours doesn't
have), set a breakpoint at "tcp_print" and "tcpport_string", in order to
check when the port number is mangled.
Hope that helps.
Regards. :)
--
Ricardo Nabinger Sanchez <rnsanchez@{gmail.com,wait4.org}>
Powered by FreeBSD
"Left to themselves, things tend to go from bad to worse."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611092350.kA9NoUbA002120>