I guess that this question is for me. Apologies for the late response, but I am traveling at the moment.
After a quick look at the source I would say that it should work. (I cannot test right now; traveling...) Can you send me a small capture that shows this behavior? Cheers, Menno -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Peter Adamson Sent: vrijdag 6 maart 2009 15:13 To: [email protected] Subject: [Wireshark-dev] Small S5066 issue Hi, I've been advised by Graeme Lunt to post to this list regarding a small issue with STANAG 5506 handling. I'm using wireshark 1.0.6 SVN Rec 27387. According to S'5066 For S_UNIDATA_IMPLICATIONS: The following four arguments shall (9) be present in the S_UNIDATA_INDICATION S_Primitive if and only if the Transmission Mode for the U_PDU is equal to Non-ARQ w/ Errors: a) The Number of Blocks in Error b) The Array of Block-Error Pointers c) The Number of Non-Received Blocks d) The Array of Non-Received-Block Pointers The final argument, U_PDU, shall (16) contain the actual received user data for delivery to the client. However when the transmission mode is "Non-ARQ / Broadcast" Wireshark interprets the U_PDU as the error block. It then looks like wireshark incorrectly think that the S_UNIDATA_IMPLICATIONS is malformed. Cheers, Peter ___________________________________________________________________________ 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
