Ok – Now it works thanks to all three of you
Best Regards
Avi
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of
Shai Shapira
Sent: Wednesday, 15 August, 2018 5:17 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Parsing openflow
Hey Avi
The
Thank you Dario and Graham
I probably did not explain well what I wanted to do.
I need to capture real traffic of openflow protocol (actually only the
specific msg-type “of-flow-add” ) and to filter in e.g. the fields surrounded
in the picture below.
It can be tshark or wireshark.
Then on the
Hey Avi
The syntax you need to use in TShark’s -e option is the same one you’d use in
the filter in Wireshark.
An easy way to find what that would be is by clicking the field you want to
export and
look in the status bar in Wireshark, the value in the brackets will be the
filter.
Example for a
On Wed, 15 Aug 2018 at 16:04, Dario Lombardo wrote:
> Try to right-click on the field you want to extract and choose "prepare a
> filter -> selected". In the upper part of wireshark a filter with the field
> you want will appear. That's the name of the field. However, if you used an
> invalid
(sorry, forgot "subject" in last mail)
Hi,
I tried to upload my small patch
Added "wireshark-win32-libs/" and "wireshark-win64-libs/" to ".gitignore"
without success. I proceeded as follows (Windows 7, starting from parent dir
after deleting previous "wireshark" dir:
Hi Ralf,
You patch is under review in Gerrit: https://code.wireshark.org/review/29147
You did not get it with a fresh clone because it has not gone through the
review process test and has not been merged in the repository.
Best regards,
Pascal.
Le mer. 15 août 2018 à 10:24, Nasilowski, Ralf a
Hi,
I tried to upload my small patch
Added "wireshark-win32-libs/" and "wireshark-win64-libs/" to ".gitignore"
without success. I proceeded as follows (Windows 7, starting from parent dir
after deleting previous "wireshark" dir:
$ git clone