#3 appears to be bug 7393 
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7393) in bugzilla.  If you 
feel the others are bugs (or enhancements), add them to bugzilla 
(https://bugs.wireshark.org/bugzilla/) so the issues don't get lost.  Of 
course, patches with fixes for those bugs/enhancements are welcome too ;)

Michael 


-----Original Message-----
From: Daniele Pala <[email protected]>
To: wireshark-dev <[email protected]>
Sent: Sun, May 19, 2013 11:35 am
Subject: [Wireshark-dev] COTP dissector problems


Hello, I've written a simple RFC 1006 implementation 
(https://github.com/danielePala/tosi) and used Wireshark to monitor the 
generated traffic. I'm seeing some problems, I attach a capture file to 
illustrate them, generated by the test cases of my implementation:

1. A lot of packets are marked as malformed, with reference to the T.125 
protocol (which I never intended to implement). See, for example, packet number 
4 of the capture file.

2. It seems that the ER (error) TPDU is not recognized, see packet number 26 
for example.

3. RFC 1006 defines a non-standard TPDU to support expedited data (see page 14 
of the standard, http://tools.ietf.org/html/rfc1006), but this is not 
recognized, see packet number 132 for example. 

Of course, the attached capture file can be also generated by re-running the 
tests of my package. 

NOTE: I'm using Wireshark 1.8.2 shipped with Debian Wheezy, however, in the 
changelogs of the more recent versions I haven't found mentions to these 
issues, so I suppose they are still there.

Best regards,
Daniele Pala 


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to