Fibre channel is a SAN protocol so it would be very likely that it
would consume a lot of bandwidth.
I.e. it is used to (primarily) act as a transport for SCSI
Normally you would not see FC on the same segment as you would have
ordinary traffic but rather only on dedicated networks in the data
On Fri, Nov 30, 2007 at 01:47:38PM -0600, Daniel Koepke wrote:
Is the MAC address in the scan validate or is it transposed or
deciphered correctly
It mostly is, but that does not say there can't be a bug somewhere.
Can the FC protocal be run over ethernet or how should I view these scans
On Thu, Nov 29, 2007 at 03:00:51PM -, Whiston, Gaetan wrote:
Hello - does anyone know how I can print or save to text file the
Protocol Hierachy window.
I'd like to save the info for baseline reporting purposes.
That functionality is not yet part of Wireshark, the only way to
keep this
Hello,
any one knows why (newest version) Wireshark cant handle Docsis packets ?
When i snif on my Cisco CMTS e.g. DHCP req. from a Cablemodem, i can only
see the ip-pack. from the server.
The rest packets are marked with : DOCSIS Mac specific[malformed packet.]
I can see that Wireshark supports
[EMAIL PROTECTED] wrote:
any one knows why (newest version) Wireshark cant handle Docsis packets ?
Can older versions handle them?
When i snif on my Cisco CMTS e.g. DHCP req. from a Cablemodem, i can only
see the ip-pack. from the server.
The rest packets are marked with : DOCSIS Mac
