Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: [Wireshark-dev] Small S5066 issue

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Peter Adamson <peter.adamson@xxxxxxxxx>
Date: Fri, 06 Mar 2009 14:12:32 +0000

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



  • Follow-Ups:
    • Re: [Wireshark-dev] Small S5066 issue
      • From: Andriesse Menno
  • Prev by Date: Re: [Wireshark-dev] Reassembling splitted PPP packets
  • Next by Date: [Wireshark-dev] packet_memcache.c doesn't compile with VC6
  • Previous by thread: Re: [Wireshark-dev] continuous packet capture
  • Next by thread: Re: [Wireshark-dev] Small S5066 issue
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation