From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: dccp@vger.kernel.org
Subject: Re: tcpdump broken wrt CsCov & CsVal parsing?
Date: Wed, 26 Sep 2007 18:27:24 +0000 [thread overview]
Message-ID: <20070926182724.GA10932@ghostprotocols.net> (raw)
In-Reply-To: <20070922144111.GE10051@ghostprotocols.net>
Em Tue, Sep 25, 2007 at 09:08:29AM +0100, Gerrit Renker escreveu:
> | On 9/23/07, Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> | > Trying to rebuild a proper test setup, so far using just loopback for
> | > simple tests I noticed this problem:
> | >
> | > Who was the last person to touch the DCCP support code in tcpdump? Care
> | > to take a look?
> | >
> | > - Arnaldo
> |
> | I'm pretty sure that would be me :-(
> |
> | I'll take a look but it won't be very soon.
> |
> ... and me too :) I know this problem - CsCov and CCVal were swapped in the
> header file. As far as I recall the maintainer had checked an update in last
> year.
>
> You didn't say which version of tcpdump you were using, I checked locally:
> * tcpdump 3.9.5 as Debian package with libpcap 0.9.5 has this swap-problem
> * tcpdump 3.9.5 built from tcpdump source, with libpcap 0.9.4 works correct
>
> Can you try tcpdump from source please and check if the problem persists?
Excellent data point, I should know better and try with upstream before
complaining. Ah, and also provide the tcpdump version:
[root@tonchinha ~]# rpm -q tcpdump
tcpdump-3.9.7-3.fc8
I'll check upstream now.
- Arnaldo
next prev parent reply other threads:[~2007-09-26 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 14:41 tcpdump broken wrt CsCov & CsVal parsing? Arnaldo Carvalho de Melo
2007-09-22 20:03 ` Ian McDonald
2007-09-25 8:08 ` Gerrit Renker
2007-09-26 18:27 ` Arnaldo Carvalho de Melo [this message]
2007-09-27 8:08 ` Gerrit Renker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070926182724.GA10932@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox