Hello and good day.
My name is David and this is my first post in the list.
I am currently studying how to develop a dissector and currently building
on top of an existing one.
The base I am using is an openflow dissector found here:
http://www.openflow.org/wp/downloads/#dissector
Created by Mr. Da
ep is to plug in the openflow dissector and modify
etype_vals and make again.
Clearly something is not right with this picture.
Hopefully this additional info clears some things.
Thanks.
On Tue, Aug 13, 2013 at 11:07 AM, DbdM Tbt wrote:
> Hello and good day.
> My name is David and this is
> being developed in trunk
>
> http://anonsvn.wireshark.org/viewvc/trunk/epan/dissectors/packet-openflow.c?revision=50623&view=markup
> written in C. It would be better to pool resources and work on that one.
> Regards
> Anders
>
> DbdM Tbt skrev 2013-08-13 06:10:
>
> Hel
ust hoping someone might have an idea how to work around the error
etype_vals error without modifying core wireshark sources.
Thank you again,
David
On Tue, Aug 13, 2013 at 1:38 PM, Anders Broman wrote:
> DbdM Tbt skrev 2013-08-13 07:11:
>
> Hi,
> From below I take it your dissector is
Good day to all.
Please bear with me as I am still learning the ins and outs of formatting
dissector output.
I have come across a discussion about hidden fields and generated fields.
http://www.wireshark.org/lists/wireshark-dev/201110/msg00257.html
I am curious about this because I have a filter r
will still occur:
C:\wireshark-1.10.1\epan/etypes.h(551) : error C2133: 'etype_vals' :
unknown size
Would building from a checkout matter? (I think it won't)
Thank you,
David
On Tue, Aug 13, 2013 at 4:02 PM, Guy Harris wrote:
>
> On Aug 12, 2013, at 10:38 PM, Anders Brom
he resources you referred.
@Harris:
About your suggestion on having a drop-down menu for the possible values.
Is the information on how to implement it available somewhere in the README
files?
Thank you very much,
David
On Tue, Aug 13, 2013 at 3:36 PM, Guy Harris wrote:
>
> On Aug 13, 201
u very much for the support.
Sincerely,
David
On Wed, Aug 14, 2013 at 1:47 AM, Guy Harris wrote:
>
> On Aug 13, 2013, at 3:00 AM, DbdM Tbt wrote:
>
> > Unfortunately I am not building from a checkout (SVN/git), instead I am
> using the wireshark source from here:
> >
Harris wrote:
>
> > On Aug 13, 2013, at 8:24 PM, DbdM Tbt wrote:
> >
> >> I would like to update I just now used an SVN checkout of wireshark and
> error C2133 will not anymore occur.
> >> I was mistaken. I didn't expect that I needed the updates to o
Good day to all,
I have been trying to figure out a behavior for a while now where the
'filter name' (third parameter of proto_register_protocol() function) does
not filter the captured messages.
For a brief background, I am studying/using an existing openflow dissector:
https://github.com/CPqD/of
matching something else?
>
> Also, you can run: "tshark -G protocols" to see if your protocol really
> is known.
>
> Gilbert
>
>
> On Wed, Aug 28, 2013 at 8:55 AM, DbdM Tbt wrote:
>
>> Good day to all,
>>
>> I have been trying to figure ou
t, array_length(ett));
>
> OFP_100_NS::init(proto_openflow);
> OFP_110_NS::init(proto_openflow);
> OFP_120_NS::init(proto_openflow);
> OFP_130_NS::init(proto_openflow);
>
> register_dissector("openflow", dissect_openflow, proto_openflow);
> }
>
>
> Regards,
12 matches
Mail list logo
