netdev - RE: [Open-FCoE] tcpdump <-> FCoE support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D3F292ADF945FB49B35E96C94C2061B90C6F54AD@nsmail.netscout.com>
Date:	Mon, 26 Jul 2010 14:27:56 -0400
From:	"Loke, Chetan" <Chetan.Loke@...scout.com>
To:	"Joe Eykholt" <jeykholt@...co.com>
Cc:	<devel@...n-fcoe.org>, <netdev@...r.kernel.org>
Subject: RE: [Open-FCoE] tcpdump <-> FCoE support

> From: Joe Eykholt [mailto:jeykholt@...co.com]
> 
> Good question.  There's no effort in progress that I know of.
> I find wireshark very handy and do tend to capture with tcpdump -w
> and then read the file with wireshark.  tshark is handy if you
> want a CLI mode.
> 
> If tcpdump interpreted FCoE frames, then we would want FC, FC-ELS,
> and FCP.  Does it already dissect any SCSI frames (e.g., iSCSI)?
> I'm not sure how much work it would be, but given tshark
> is around, I don't think it's that important.
> 
Oki thanks. I'll play with tshark. If tshark handles the FIP/FC
discovery business then that's perfect. I don't have a FCoE target
configured yet. I just sent a raw fcoe-frame to check how tcpdump
responds.

> It could at least be changed to print out FCoE instead of 0x8906,
> and FIP instead of 0x8914.
> 
Agreed.


> 	Joe
Chetan Loke
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html