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] Trouble adding an ASN.1 based dissector

From: "ronnie sahlberg" <ronniesahlberg@xxxxxxxxx>
Date: Sun, 25 Nov 2007 07:09:31 +1100
If Im not mistaken   T124 is encoded with aligned PER while T125 is
BER   so oyu also need to change the flags to asn2wrs to generate
a PER dissector.
You then  also need to look at how other PER dissectors set whether it
is aligned or unaligned PER from the template file.


On Nov 24, 2007 8:26 PM, Stephen Fisher <stephentfisher@xxxxxxxxx> wrote:
> I'm stumbling through (is there a README somewhere?) trying to add my
> first ASN.1 based dissector (T.124 / Generic Conference Control) to
> Wireshark and I'm running into the following error.  I mostly copied the
> asn1/t124 files from asn1/t125.  This is another layer in a Microsoft
> Remote Desktop Protocol (RDP) session above t.125.
>
> sfisher@shadow:/usr/local/src/wireshark/asn1/t124>make generate_dissector
> python ../../tools/asn2wrs.py \
>         -b -X -T \
>         -p t124 \
>         -c ./t124.cnf \
>         -s ./packet-t124-template \
>         -D . \
>          GCC-PROTOCOL.asn
> ASN.1 to Wireshark dissector compiler
> Traceback (most recent call last):
>   File "../../tools/asn2wrs.py", line 7671, in ?
>     eth_main()
>   File "../../tools/asn2wrs.py", line 7602, in eth_main
>     ast.extend(yacc.parse(f.read(), lexer=lexer, debug=pd))
>   File "/usr/local/src/wireshark/tools/yacc.py", line 346, in parse
>     tok = self.errorfunc(errtoken)
>   File "../../tools/asn2wrs.py", line 7455, in p_error
>     raise ParseError(t, input_file)
> __main__.ParseError: GCC-PROTOCOL.asn:54: Unexpected token UniversalString('UniversalString')
> make: *** [packet-t124.c] Error 1
>
> Am I doing something wrong, or does it not like part of the .asn file?
>
> Also, how do I go about creating the t.124.cnf file?  (My attempt above
> was using the t125.cnf file)
>
>
> Thanks,
>
> Steve
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>