From: Hagen Paul Pfeifer <hagen@jauu.net>
To: "Loke, Chetan" <Chetan.Loke@netscout.com>
Cc: devel@open-fcoe.org, netdev@vger.kernel.org
Subject: Re: tcpdump <-> FCoE support
Date: Mon, 26 Jul 2010 21:22:14 +0200 [thread overview]
Message-ID: <20100726192214.GA2937@nuttenaction> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B90C6F53AE@nsmail.netscout.com>
* Loke, Chetan | 2010-07-26 13:30:13 [-0400]:
>13:08:21.907971 00:yy:yy:yy:yy:yy (oui Unknown) > 00:xx:xx:xx:xx:xx (oui
>Unknown), ethertype Unknown (0x8906)
>
>On: tcpdump-4.0.0-3, tcpdump doesn't seem to have FCoE support(unless I
>capture it and pipe it to wireshark). Is there any effort currently in
>progress on adding FCoE parsers?
That's no kernel issue, it is purely related to userland tools such as
tcpdump/wireshark/whatever.
Hagen
prev parent reply other threads:[~2010-07-26 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 17:30 tcpdump <-> FCoE support Loke, Chetan
[not found] ` <D3F292ADF945FB49B35E96C94C2061B90C6F53AE-2s2rCY1e8UXHBhWB4kaBDUEOCMrvLtNR@public.gmane.org>
2010-07-26 17:57 ` Joe Eykholt
[not found] ` <4C4DCCA6.5060206-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-07-26 18:27 ` Loke, Chetan
2010-07-26 19:22 ` Hagen Paul Pfeifer [this message]
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=20100726192214.GA2937@nuttenaction \
--to=hagen@jauu.net \
--cc=Chetan.Loke@netscout.com \
--cc=devel@open-fcoe.org \
--cc=netdev@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