Maybe an even better idea would be to regenerate them using ASN2ETH instead...
On 8/22/05, ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote:
> Hm.
>
> Maybe we should regenerate RANAP using ETH2ASN.
> It is usually quite easy to do this.
>
>
> Anyone has a few RANAP traces and a pointer to the ASN specification?
>
>
>
> On 8/22/05, Guy Harris <gharris@xxxxxxxxx> wrote:
> > chao_zhao@xxxxxxxxxxx wrote:
> >
> > > I am a new user to Ethereal applied to RANAP interpreting.As you know
> > > that Ethereal now can support UMTS RANAP protocol decoding.RANAP is
> > > encoded in ASN.1 PER ALIGNED syntax.Who can tell me which ASN compiler
> > > is used by Ethereal?
> >
> > In the case of RANAP, the compiler is called "Martin Held". :-)
> >
> > I.e., the RANAP dissector was built by hand by Martin Held (and assorted
> > other people). (It doesn't even use packet-per.c.)
> >
> > Other ASN.1 (BER, DER, PER)-based dissectors were either written by hand
> > (using packet-ber.c or packet-per.c routines, or the old asn1.c
> > routines), or generated by the asn2eth compiler, which is part of
> > Ethereal, and compiles ASN.1 specifications (and some additional
> > information) into protocol dissectors. (Note that it compiles them into
> > protocol dissectors, *NOT* into protocol implementations of the sort
> > that would be useful in a machine on the network. It could perhaps be
> > made to generate such a protocol implementation, but that wasn't what it
> > was designed for.)
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev@xxxxxxxxxxxx
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
>
