Wireshark-bugs: [Wireshark-bugs] [Bug 8505] New: openSAFETY: New reassemble functionality, as we
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 20 Mar 2013 16:41:38 +0000
Bug ID 8505
Summary openSAFETY: New reassemble functionality, as well as minor bugfixes
Classification Unclassified
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter rknall@gmail.com 

Build Information:
TShark 1.9.2 (SVN Rev 48440 from /trunk)

Copyright 1998-2013 Gerald Combs <gerald@wireshark.org> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GLib 2.32.3, with libpcap, with libz 1.2.3.4, with POSIX
capabilities (Linux), without libnl, with SMI 0.4.8, with c-ares 1.7.5, with
Lua
5.1, without Python, with GnuTLS 2.12.14, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP.

Running on Linux 3.2.0-38-generic, with locale de_AT.UTF-8, with libpcap
version
1.1.1, with libz 1.2.3.4.
Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz

Built using gcc 4.6.3.
--
The attached update implements various improvements and bugfixes for the
current wireshark dissector:

 - New reassemble of segmented SSDO transfer packages, depends on #8502
   * Extended Parameter detection and header dissection
   * Parameter download dissection and Index/SubIndex dissection

 - SNMT SN_FAIL -> New error message added
 - SSDO Dictionary -> New entries for specific module parameters 
 - SSDO Sequence Nr gets correctly dissected now
 - SercosIII/UDP frame ordering preference added
 - Adding error message with one argument
 - Corrected Assembly of CT in SPDO and SSDO
 - read_lowhigh_order in correctly reading 4 byte entries
 - SSDO Sender/Receiver was mixed up, as well as server - client
 - SNMD Sender/Receiver was mixed up, as well as master - slave 
 - Frame Detection wrongly jumped by frameLength / changed to 2
 - Display of new datasource reduced to correctly acknowledged frames

You are receiving this mail because:
  • You are watching all bug changes.