Home Forums Technical discussions Wireshark dissectore for OF not running in new VM

Tagged: 

This topic contains 4 replies, has 2 voices, and was last updated by  Milstein Munakami 5 years, 2 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #883

    Milstein Munakami
    Participant

    Hi Srini,

    Why the new VM is not supporting OF dissector in Wireshark please check and let me know how to fix this in my Ubuntu 12.04 VM. I can’t able to filter the packets in wireshark with of !

    Thanks,
    Milson

    #885

    Srini Seetharaman
    Participant

    Hi Milson
    With the new Ubuntu 14.04 VM, we switched to using Wireshark 1.11.3 that has native OF parsing support. You don’t need a separate dissector anymore. Can you upgrade your wireshark to that version using these instructions?

    sudo apt-get -y remove wireshark
    sudo apt-get -y install libgtk-3-dev libqt4-dev flex bison
    wget http://www.wireshark.org/download/src/wireshark-1.11.3.tar.bz2
    tar xvfj wireshark-1.11.3.tar.bz2
    cd wireshark-1.11.3
    ./configure
    make -j4
    sudo make install
    cd ..
    sudo echo “/usr/local/lib” >> /etc/ld.so.conf
    sudo ldconfig

    #892

    Milstein Munakami
    Participant

    Hi Srini,

    Still I am getting the same issue even though the wireshark is 1.11.3.

    Wireshark Info

    Thanks,
    Milson

    #896

    Srini Seetharaman
    Participant

    Hi Milson
    With the new version, I don’t think you will see a separate plugin added. Are you not seeing the OpenFlow packets being parsed?

    Srini.

    #898

    Milstein Munakami
    Participant

    To Display Filter in latest wireshark:

    A complete list of OpenFlow display filter fields can be found in the display filter reference (Note: this page still doesn’t exist; most likely it will only be created on the release date of Wireshark 1.12) or listed with the following command:

    tshark -G fields | grep -i openflow

    Show only the OpenFlow based traffic:

    openflow

    Show only the OpenFlow 1.3 based traffic:

    openflow_v4

    Seems the filter keyword is now changed!!!

    Thanks Srini,

    Milson

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.