Then I'm really confused about how to hook a TCP Port for decoding if
it's not done via Dissector? I know that's how the development guide
suggested & several of TCP based dissectors worked when we wrote our
internal dissectors. Our dissectors show up in the list of enabled
Protocols. Has Wireshark core functionality changed?
- Thanks in advance.
- Tim
> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jaap Keuter
> Sent: Friday, January 18, 2008 2:42 PM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] Registered Protocols?
>
> Hi,
>
> This has nothing to do with dissectors. These are TCP port
> numbers resolved to the corresponding service names, found in
> the services file.
>
> Thanx,
> Jaap
>
> Timothy.Cook@xxxxxxxxxxx wrote:
> > With the 99.7 release of Wireshark at least two of our internal
> > disectors have been disabled (for lack of better term). How can I
> > disable the disectors for "cadlock2" (port 1000) & "search agent"
> > (port
> > 1234) (these are the names in the display->INFO column).
> I've looked
> > though the list of "enabled protocols".
> >
> > Any information would be greatly appreciated.
> >
> >
> > - Tim
> >
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>