Wireshark · Wireshark-dev: Re: [Wireshark-dev] Problems when trying to compile a new ASN.1 dissector

[Larry LeCrabe <spice_cowboy@xxxxxxxxxxx>]

Hi,

Here is some raw asn.1 as my system gaves me.

I have tried to "autogen.sh, configure then make" but it still doesn't work :
Wireshark still displays it as BER, and I can't force my dissector it the "Decode As..." dialog because the option doesn't appear there.

I'm sure there is something to add somewhere to make it appear in that dialog, but I don't know what.

Thanks !
Franck.


> From: a.broman@xxxxxxxxx
> To: wireshark-dev@xxxxxxxxxxxxx
> Date: Mon, 27 Jul 2009 22:47:54 +0200
> Subject: Re: [Wireshark-dev] Problems when tryingto compile anew ASN.1dissector
>
> Also do you have a small example trace to try it out with?
> Regards
> Anders
>
> -----Ursprungligt meddelande-----
> Från: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Jaap Keuter
> Skickat: den 27 juli 2009 21:19
> Till: Developer support list for Wireshark
> Ämne: Re: [Wireshark-dev] Problems when tryingto compile anew ASN.1dissector
>
> Hi,
>
> Adding an automake based dissector requires you to build Wireshark as the
> first
> time, so autogen.sh, configure then make. See:
> http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcBuildFirstTime.html
>
> Thanx,
> Jaap
>
> Larry LeCrabe wrote:
> > I have done all of your instructions but it still doesn't work.
> >
> > To prevent conflicts, I flushed all previous stuff and untarred
> > wireshark-1.1.2.tar.gz to the directory.
> >
> > My dissector seems to have been compiled, as there is a
> > 'libdissectors_la-packet-hi2.lo' in the epan/dissectors directory, but
> > when I run wireshark, I don't see anything like hi2 or HI2Operations in
> > the "Decode As..." dialog, and my asn1 stuff is still displayed as BER...
> >
> > I don't have the software to compile it on Windows, and therefore,
> > cannot tell you if it work by editing Makefile.nmake
> > But in Linux, all seems to go fine... I'm not a expert in compilating
> > but it seems to be a linker issue, with my dissector generated but not
> > included into the whole.
> >
> > Can you please try to built it on Windows, so I'm sure that my problem
> > is not Linux-specific or my-computer-specific ?
> >
> > Thanks in advance,
> > Franck.
> >
> >
> > ------------------------------------------------------------------------
> > From: a.broman@xxxxxxxxx
> > To: wireshark-dev@xxxxxxxxxxxxx
> > Date: Mon, 27 Jul 2009 16:54:04 +0200
> > Subject: Re: [Wireshark-dev] Problems when trying to compile anew
> > ASN.1dissector
> >
> > Hi,
> >
> > I think you can get rid of:
> >
> > #include "packet-wlancertextn.h"
> >
> > #include "packet-x509af.h"
> >
> > #include "packet-x509ce.h"
> >
> > #include "packet-x509sat.h"
> >
> > In the template file.
> >
> >
> >
> > I’m not to familiar with the make files on linux but I think you need to
> > add hi2 to makefile.am and makefile.nmake
> >
> > In the asn1 dir. At least on windows if you run nmake –f makefile.nmake
> > hi2 in the asn1 dir it would generate the dissector
> >
> > And copy it to epan/dissectors (packet-hi2.[ch]) you don’t need a .h
> > file unless you are exporting stuff.
> >
> >
> >
> > Then to compile the resulting dissector you need to add it to
> > makefile.common in epan/dissectors and run make
> >
> > In the top dir.
> >
> > Hope this helps
> >
> > Anders
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > *Från:* wireshark-dev-bounces@xxxxxxxxxxxxx
> > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] *För *Larry LeCrabe
> > *Skickat:* den 27 juli 2009 16:06
> > *Till:* wireshark-dev@xxxxxxxxxxxxx
> > *Ämne:* Re: [Wireshark-dev] Problems when trying to compile anew
> > ASN.1dissector
> >
> >
> >
> > Hi Anders, and thank you for replying so fast !
> >
> > The protocol i'm wishing to implement is ETSI 201 671 - HI2Operations
> >
> > At the end of the hi2.asn file, I have copy/pasted only the 6 required
> > definitions from 3GPP 33.108 rather to import the whole stuff.
> >
> > I was planning to do the same for EN 301 040, but we don't use TETRA, so
> > I commented the import directive and associated definitions throughout
> > the asn1 declaration.
> >
> > Please note that the hi2.asn is surely the cleanest of the whole
> > zipfile, the others are certainly more suspicious...
> >
> >
> > Good luck !
> > Franck.
> >
> >
> > ------------------------------------------------------------------------
> >
> > From: a.broman@xxxxxxxxx
> > To: wireshark-dev@xxxxxxxxxxxxx
> > Date: Mon, 27 Jul 2009 15:10:45 +0200
> > Subject: Re: [Wireshark-dev] Problems when trying to compile a new
> > ASN.1dissector
> >
> > Hi,
> >
> > Which ETSI protocol is it?
> >
> > Could you zip your asn1/ folder and attach it?
> >
> > Regards
> >
> > Anders
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > *Från:* wireshark-dev-bounces@xxxxxxxxxxxxx
> > [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] *För *Larry LeCrabe
> > *Skickat:* den 27 juli 2009 14:27
> > *Till:* wireshark-dev@xxxxxxxxxxxxx
> > *Ämne:* [Wireshark-dev] Problems when trying to compile a new
> ASN.1dissector
> >
> >
> >
> > Hi there,
> >
> > I'm wishing to compile a new ASN.1 dissector, but I'm completely screwed
> > with Asn2wrs...
> >
> > What I have done since the beginning :
> > - Read the asn2wrs wiki at 'http://wiki.wireshark.org/Asn2wrs'
> > - Copy/Paste the ETSI ASN.1 description into a text file (Hopefully, no
> > need to replace odd keywords!)
> > - Edit a conformance file, using wlancertexn.cnf as reference, but
> > definitively not understanding what I was editing...
> > - Edit a template file, still using wlancertexn as reference... and
> > still not understanding...
> > - Looking for a 'Makefile.common' located in the asn1/ directory, and a
> > 'Makefile' from another asn.1 dissector, but they *do not* exist in any
> > source version of wireshark I have tried... so I have edited all the
> > Makefile.* to add a subdir in the list for my dissector.
> > - Trying to './configure' then 'make', but when 'make' comes to my
> > dissector, it desperately fails indicating my dissector is "defined but
> > not used"...
> >
> > I know I am doing it like an asshole, but it is the only way I know today.
> >
> > May someone helps me ?
> >
> > Thanks you,
> > Franck.
> >
> >
>
> ___________________________________________________________________________
> 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

---

Discutez sur Messenger où que vous soyez ! Mettez Messenger sur votre mobile !

Attachment: 10001000000302-20090529173556-4-000.raw
Description: Binary data