| Bug ID |
10177
|
| Summary |
Cannot see packets in Wireshark properly for 11ac capture with Cisco3700 + WLC2500 setup (Wireshark running on Win7)
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.11.x (Experimental)
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 12790 [details]
CiscoRemoteCapture
Build Information:
wireshark 1.11.3 (v1.11.3-0-g1dd5d3a from master)
Copyright 1998-2014 Gerald Combs <[email protected]> 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 GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 2.12.18, with Gcrypt 1.4.6,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Apr 15 2014),
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), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz, with 3996MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Followed steps mentioned at
https://supportforums.cisco.com/document/75236/collecting-wireless-sniffer-trace-using-cisco-lightweight-ap-sniffer-mode
Setup used is Cisco WLC 2500 + Cisco LAP 3700 in Sniffer mode.
Win7 (64-bit) machine running Wireshark (v1.11.3) is connected over Ethernet
with capture filter "udp port 5555".
The packets after decode with peekremote do not show up correctly. The beacons
and other some control packets (RTS/CTS) come up fine, but Data packets are not
coming up correctly. Any idea what might be the problem ?
I have also tried with v1.6.8 as mentioned in the Cisco link, but see the same
problem. TCP traffic is captured and all TCP data pkts show up as IPv4 without
any 802.11 info in it and TCP ACKs show up as LLC.
You are receiving this mail because:
- You are watching all bug changes.