From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Felix Obenhuber <felix@obenhuber.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [RFC] CAN FD support part 2 - ideas and commented source
Date: Mon, 07 May 2012 20:03:06 +0200 [thread overview]
Message-ID: <4FA80E5A.7070805@hartkopp.net> (raw)
In-Reply-To: <CAJsOQGNcdSyMjyH3XxZjhcmnZBKY_vBsb3+tEyxcuyxF7kJk1A@mail.gmail.com>
On 07.05.2012 13:51, Felix Obenhuber wrote:
> On Thu, May 3, 2012 at 3:22 PM, Kurt Van Dijck <kurt.van.dijck@eia.be> wrote:
>>> This has a big advantage when thinking about wireshark & friends.
>> I must have missed something here. ETH_P_CANFD value somewhere in struct skb
>> is something kernel specific. Does wireshark look inside kernel?
>
> No, it doesn't. The detection of a SocketCAN socket/interface is done
> very hacky with the interface name in pcap.
>
> pcap-linux.c:432:
>
> #ifdef PCAP_SUPPORT_CAN
> if (strstr(device, "can") || strstr(device, "vcan")) {
> return can_create(device, ebuf);
> }
> #endif
Oh, oh.
I like to have at least one vcan interface named 'helga' on my system.
Obviously i won't have fun with pcap %-/
Regards,
Oliver
next prev parent reply other threads:[~2012-05-07 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FA242D0.2070604@hartkopp.net>
2012-05-03 11:14 ` [RFC] CAN FD support part 2 - ideas and commented source Oliver Hartkopp
2012-05-03 12:37 ` Kurt Van Dijck
2012-05-03 12:50 ` Oliver Hartkopp
2012-05-03 13:22 ` Kurt Van Dijck
2012-05-07 11:51 ` Felix Obenhuber
2012-05-07 18:03 ` Oliver Hartkopp [this message]
2012-05-03 18:01 ` Wireshark / libpcap - was " Oliver Hartkopp
2012-05-04 9:29 ` Kurt Van Dijck
2012-05-04 9:59 ` Oliver Hartkopp
2012-05-07 12:19 ` Felix Obenhuber
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=4FA80E5A.7070805@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=felix@obenhuber.de \
--cc=linux-can@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