Wireshark-bugs: [Wireshark-bugs] [Bug 10918] New: Problem with CAPWAP fragment for decode TCP st

Date: Wed, 04 Feb 2015 20:45:56 +0000
Bug ID 10918
Summary Problem with CAPWAP fragment for decode TCP stream
Product Wireshark
Version 1.99.x (Experimental)
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 13427 [details]
example of tcp flow fragmented into 2 capwap packets.

Build Information:
Version 1.99.1 (v1.99.1-0-g4c229ca from master)

Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.1, with WinPcap (4_1_3), with libz 1.2.5, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, without PortAudio,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz, with 10205MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 30501

--
With CAPWAP fragmented packets, there are problems on the interpretation of the
inner TCP flow. If a TCP packet is sent into 2 CAPWAP fragment, the second
fragment is marked TCP Out-Of-Order.

Attached a example of TCP flow generate with IPERF. In an example I use a MTU
of inner traffic set to 1400 bytes.


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