:
[cid:image001.png@01D434C8.F1C57460]
Good luck
From: Avi Cohen (A)<mailto:avi.co...@huawei.com>
Sent: Wednesday, August 15, 2018 17:08
To: Developer support list for Wireshark<mailto:wireshark-dev@wireshark.org>
Subject: Re: [Wireshark-dev] Parsing openflow
Hi Dario
I can easily create
tice with easier fields (I suggest ip.src) if you're not used to
those tshark options.
No need to create a filter, select the field in the packet tree and look for
the field name in the status bar in parenthesis.
On Wed, Aug 15, 2018 at 4:08 PM Avi Cohen (A)
mailto:avi.co...@huawei.com&g
could do the job.
On Tue, Aug 14, 2018 at 1:19 PM Avi Cohen (A)
mailto:avi.co...@huawei.com>> wrote:
Hi
I need to capture open-flow msgs (e.g FLOW_MOD to add new flows) from
controller to vSwitch ,
And to generate e.g. a *file* which its rows are the captured flows and its
columns a
Hi
I need to capture open-flow msgs (e.g FLOW_MOD to add new flows) from
controller to vSwitch ,
And to generate e.g. a *file* which its rows are the captured flows and its
columns are the flow header fields e.g. column 1 source-mac , column 2
dest-mac , column 3 source-IP etc.. - whenev
