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
Hi Avi
Have a look at tshark and its -E and -e options. That could do the job.
On Tue, Aug 14, 2018 at 1:19 PM Avi Cohen (A) 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 capt
Thank you Dario
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of
Dario Lombardo
Sent: Tuesday, 14 August, 2018 2:50 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Parsing openflow
Hi Avi
Have a look at tshark and its -E and -e options. That
Hi folks,
I am running into a problem where a component of an FT_UINT48 and
which is a 3-bit field but I am using a CF_FUNC.
However, Wireshark 2.6.2 is complaining that it is an FT_UINT48 but is
being displayed as an STR_UNICODE.
How do I resolve this?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--
On Tue, Aug 14, 2018 at 7:42 PM, Richard Sharpe
wrote:
> Hi folks,
>
> I am running into a problem where a component of an FT_UINT48 and
> which is a 3-bit field but I am using a CF_FUNC.
>
> However, Wireshark 2.6.2 is complaining that it is an FT_UINT48 but is
> being displayed as an STR_UNICODE
