Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Trouble adding an ASN.1 based dissector

From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Sat, 24 Nov 2007 11:04:25 +0100
Hi,
Where did you get the ASN1 tile? From the ITU site?
Can you send me your ../asn1/t.124 directory?
There is something on line 54 in the asn1 file asn2wrs does not like...
Regards
Anders

-----Ursprungligt meddelande-----
Från: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Stephen Fisher
Skickat: den 24 november 2007 10:26
Till: wireshark-dev@xxxxxxxxxxxxx
Ämne: [Wireshark-dev] Trouble adding an ASN.1 based dissector

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