Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 6534] New: Ethernet OUI name resolution is not working properly

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6534

           Summary: Ethernet OUI name resolution is not working properly
           Product: Wireshark
           Version: SVN
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: christopher.maynard@xxxxxxxxx


Build Information:
Version 1.7.0 (SVN Rev 39701 from /trunk)

Compiled (32-bit) with GTK+ 2.22.1, with Cairo 1.10.2, with Pango 1.28.3, with
GLib 2.26.1, with WinPcap (version unknown), with libz 1.2.5, without POSIX
capabilities, with threads support, with SMI 0.4.8, with c-ares 1.7.1, with Lua
5.1, without Python, with GnuTLS 2.10.3, with Gcrypt 1.4.6, with MIT Kerberos,
with GeoIP, with PortAudio V19-devel (built Oct 13 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, with AirPcap 4.1.1 build 1838.

Built using Microsoft Visual C++ 10.0 build 40219

--
Ethernet OUI name resolution is not working properly in all cases.  Sometimes
it resolves to IP addresses instead of real OUI names.

It seems to be very easy to replicate, but to illustrate, load the
fuzz-2011-09-28-20105.pcap capture file attached to bug 6403 and notice that
the for the very first packet, the 08:00:20 OUI is resolved to 204.252.103.11
instead of as, "Oracle".

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.