From: Ico Doornekamp <can@zevv.nl>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can <linux-can@vger.kernel.org>,
yegorslists <yegorslists@googlemail.com>
Subject: Re: CAN libpcap capture endianess
Date: Thu, 12 Sep 2013 11:31:16 +0200 [thread overview]
Message-ID: <1378978095-sup-4073@pruts.nl> (raw)
In-Reply-To: <523185C4.1020208@pengutronix.de>
* On 2013-09-12 11:13:40 +0200, Marc Kleine-Budde wrote:
> On 09/12/2013 11:09 AM, Ico Doornekamp wrote:
>
> >> They are assuming the wrong endianes for your capture file. Yegor's
> >> capture file, which comes in another format, is interpreted correctly.
> >
> > Sorry, I was not completely clear on this: I did the capturing on the
> > slcan0 interface from wireshark, so I did not make a capture file first.
>
> In your original mail you've captured with wireshark, too, but written
> into a file. Now you are capturing with wireshark directly.
Correct. Yesterday I did not have access to the test setup, but today
I'm back at the lab.
> I assume the same capturing engine (that one in wireshark) is involved
> in both workflows and the same error is triggered in the
> interpretation/dissection process.
That's what I'm thinking as well. But the confusion arose because of the
dump I received from Yegor, which was decoded correctly by wireshark.
I've long learned that is usually safest to assume that strange errors
originate from myself instead of questioning other peoples software, but
in this case it seems that wireshark is at fault.
--
:wq
^X^Cy^K^X^C^C^C^C
next prev parent reply other threads:[~2013-09-12 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 17:42 CAN libpcap capture endianess Ico
2013-09-11 18:22 ` Marc Kleine-Budde
2013-09-11 18:30 ` Ico Doornekamp
2013-09-11 18:38 ` Marc Kleine-Budde
2013-09-11 18:53 ` Ico Doornekamp
2013-09-11 19:22 ` Oliver Hartkopp
2013-09-11 19:17 ` Oliver Hartkopp
2013-09-11 19:34 ` Marc Kleine-Budde
2013-09-11 19:37 ` Marc Kleine-Budde
2013-09-11 20:05 ` Ico Doornekamp
2013-09-11 20:11 ` Marc Kleine-Budde
2013-09-12 6:52 ` Ico Doornekamp
2013-09-12 8:00 ` Marc Kleine-Budde
2013-09-12 8:47 ` Ico Doornekamp
2013-09-12 8:52 ` Marc Kleine-Budde
2013-09-12 9:09 ` Ico Doornekamp
2013-09-12 9:13 ` Marc Kleine-Budde
2013-09-12 9:31 ` Ico Doornekamp [this message]
2016-05-10 19:25 ` Ico Doornekamp
2016-05-11 7:40 ` Oliver Hartkopp
[not found] ` <1462952665-sup-1016@pruts.nl>
2016-05-11 8:17 ` Oliver Hartkopp
2016-05-11 12:28 ` Ico Doornekamp
2016-05-11 13:25 ` Oliver Hartkopp
2016-05-11 17:01 ` Ico Doornekamp
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=1378978095-sup-4073@pruts.nl \
--to=can@zevv.nl \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=yegorslists@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.