ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Dissector from metafile?

From: Justin Guan <jguan@xxxxxxxxxxxxxxx>
Date: Fri, 17 Apr 2009 15:47:34 -0700 (PDT)
Sorry, it was the wrong link. Here is the corrected link:

http://www.protomatics.com/wireshark_dissector.html

Justin

--- On Fri, 4/17/09, Justin Guan <jguan@xxxxxxxxxxxxxxx> wrote:

> From: Justin Guan <jguan@xxxxxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Dissector from metafile?
> To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
> Date: Friday, April 17, 2009, 7:19 AM
> Hi Tamas,
> 
> Check out the Wireshark dissector generator:
> 
> http://www.protomatics.com/wireshark_disector.html
> 
> Full spec and examples of TSN.1 can be found at:
> 
> http://www.protomatics.com/TSN1_Spec.pdf
> 
> Justin
> 
> --- On Fri, 4/17/09, Tamas Somogyi
> <tsomogyi@xxxxxxxxxxxxxxxxx> wrote:
> 
> > From: Tamas Somogyi <tsomogyi@xxxxxxxxxxxxxxxxx>
> > Subject: [Wireshark-dev] Dissector from metafile?
> > To: wireshark-dev@xxxxxxxxxxxxx
> > Date: Friday, April 17, 2009, 3:52 AM
> > Hi,
> > 
> > I'm new in Wireshark development; I've just
> coded
> > my first dissector for
> > one of our company-specific protocols, and I'm
> going to
> > write the next.
> > 
> > However my impression is, that simple protocols might
> be
> > described
> > pretty well by structured texts/files (e.g. XML
> files),
> > because most of
> > my code is just about formatting the data (texts,
> values,
> > etc.) and
> > defining the tree structure.
> > Defining protocol dissectors in text metafiles for
> > Wireshark would have
> > many advantages: no need for installing the whole
> > development
> > environment for adding just a simple protocol,
> moreover it
> > would be no
> > software development work any more to add protocol to
> > Wireshark.
> > 
> > Is there any existing possibility to define dissector
> from
> > meta-file
> > instead of coding, or is there any ongoing development
> in
> > this
> > direction?
> > 
> > Thanks,
> > Tamas
> >
> ___________________________________________________________________________
> > Sent via:    Wireshark-dev mailing list
> > <wireshark-dev@xxxxxxxxxxxxx>
> > Archives:   
> http://www.wireshark.org/lists/wireshark-dev
> > Unsubscribe:
> > https://wireshark.org/mailman/options/wireshark-dev
> >             
> >
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list
> <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe:
> https://wireshark.org/mailman/options/wireshark-dev
>             
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe