Hi,
Hard to tell without seeing the register routine. Are you sure there is a valid handle
when you do the dissector_add()?
BR
Anders
________________________________
Från: wireshark-dev-bounces@xxxxxxxxxxxxx genom Jared King
Skickat: on 2007-01-10 07:04
Till: wireshark-dev@xxxxxxxxxxxxx
Ämne: [Wireshark-dev] Dissector plugin not registering properly.
I am writing a dissector plugin for an inhouse message protocol. I can not
get it to dissect the packets it should.
Wireshark sees the plugin, it brings up the preference I have created to set
the port number manually. Initially I use a line like:
"dissector_add("tcp.port", 5555, my_protocol_handle_handle)"
Then if the user wishes to change the port number they do it in preferences
and I delete the old and add the new.
For some reason it does not dissect the packets. The packets are being
received but just interpreted as TCP packets and not going any further.
The protocol connects at my side (side running wireshark) on port 5555 by
default and uses a random port at the other end. Is it possible that
this could
be causing troubles. Do both the ports (source and destination) need to
match
or just one or the other?
What else could I be doing wrong?
Thanks
Jared King
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
<<winmail.dat>>