[Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread Dr. Uwe Girlich
Hello! I just added (with revision 32202) a new dissector plugin: INTERLINK (yes, I know, a too general name but that's what it is called by BMW). This protocol is used in BMW cars (real and simulated) for all kinds of gadget communication (for example to and from the combination display or the

Re: [Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread Jaap Keuter
Hi, Well, it broke the build so you may want to check into that. Also the design desision to make it a plugin is a poor one. Single file dissectors should be added to the build in set, otherwise we would drown in the maintenane of all these 'little used' plugins. Thanks, Jaap Send from my

Re: [Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread Joerg Mayer
On Tue, Mar 16, 2010 at 08:16:44AM +0100, Dr. Uwe Girlich wrote: I just added (with revision 32202) a new dissector plugin: INTERLINK (yes, I know, a too general name but that's what it is called by BMW). This protocol is used in BMW cars (real and simulated) for all kinds of gadget

Re: [Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread ronnie sahlberg
On Tue, Mar 16, 2010 at 8:13 PM, Joerg Mayer jma...@loplof.de wrote: On Tue, Mar 16, 2010 at 08:16:44AM +0100, Dr. Uwe Girlich wrote: I just added (with revision 32202) a new dissector plugin: INTERLINK (yes, I know, a too general name but that's what it is called by BMW). This protocol is

Re: [Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread Aniruddha A
Message: 4 Date: Tue, 16 Mar 2010 10:06:25 +0100 From: Jaap Keuter jaap.keu...@xs4all.nl Subject: Re: [Wireshark-dev] INTERLINK dissector plugin added To: Developer support list for Wireshark wireshark-dev@wireshark.org Message-ID: 98f0fbc3-9e06-4f42-bcb9-5c098deb9...@xs4all.nl Content-Type

Re: [Wireshark-dev] INTERLINK dissector plugin added

2010-03-16 Thread Ed Beroset
Aniruddha A aniruddh...@gmail.com wrote: How to decide whether a dissector has to be a plugin or a build-in ? Is it based on the code size ? I have also created a plugin (based on a protocol which is in draft state in IETF) and the code size is small, I was about to raise patch request on