Wireshark · Wireshark-dev: [Wireshark-dev] How to avoid dissection based on port defined by a different dissector?

Wireshark-dev: [Wireshark-dev] How to avoid dissection based on port defined by a different dis

Date: Wed, 15 Dec 2010 15:02:31 -0500

I have a dissector plugin that is registered with port A. Once in a while, this dissector is not kicking in. It looks like it "overpowered" by a dissector with registered port 3503 (lsp-ping). It looks like port 3503 is defined in epan\dissectors\packet-mpls-echo.c(39):#define UDP_PORT_MPLS_ECHO 3503. Can somebody suggest how to avoid this trap?

Thanks

Follow-Ups:
- Re: [Wireshark-dev] How to avoid dissection based on port defined by a different dissector?
  - From: Christopher Maynard
- Re: [Wireshark-dev] How to avoid dissection based on port defined by a different dissector?
  - From: Stephen Fisher

Prev by Date: Re: [Wireshark-dev] New network interface card integration
Next by Date: Re: [Wireshark-dev] [work in progress / stuck] improved dissection for VNC (correct hextile encoding, correct desegmentation)
Previous by thread: Re: [Wireshark-dev] Problems with release 1.4.2?
Next by thread: Re: [Wireshark-dev] How to avoid dissection based on port defined by a different dissector?
Index(es):
- Date
- Thread