| Bug ID |
10195
|
| Summary |
Why are Ethernet II packets incorrectly identified as 802.3?
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.8.7
|
| Hardware |
Other
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Capture file support (libwiretap)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 12816 [details]
explained in the description
Build Information:
Version 1.8.7 (SVNRev 49382 from /trunk-1.8)
Copyright 1998-2013 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 (32-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, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built May 17 2013), 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.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
0
I am sending Ethernet II frames with Destination MAC address of
02:29:99:99:00:21
wireshark is decoding those as 802.3 while two-octet field after Source MAC
address is 0x8902. It seems The most significant bits of destination MAC
address have special functions according to the IEEE 802 specification. Hence I
changed the MAC address to 00:29:99:99:00:21 but couldn't solve the issue. I
changed it again to one of the previously working MAC of 00:60:64:74:66:68 and
workrd fine
attached file named 02_29_99_CFM packet is the one with the issue. I am sending
CFM packet destined to 00:29:99:99:00:21 and it is being decoded as 802.3.
File named 00_60_64_CFM packets is the same CFM packet but with destination MAC
address of 00:60:64:74:66:68.
You are receiving this mail because:
- You are watching all bug changes.