http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2152
Summary: IEEE locally assigned addresses reported as belonging to
Microsoft
Product: Wireshark
Version: 0.99.6
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: markzzzsmith@xxxxxxxxxxxx
Build Information:
TShark 0.99.6
Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 with GLib 2.14.1, with libpcap 0.9.8, with libz 1.2.3, with libpcre
7.3, without Net-SNMP, without ADNS, without Lua, with GnuTLS 2.0.0, with
Gcrypt
1.2.4, with Heimdal Kerberos.
Running on Linux 2.6.23-ARCH, with libpcap version 0.9.8.
Built using gcc 4.2.1.
--
Hi,
I've randomly chosen some locally assigned IEEE / MAC addresses for a virtual
network I've setup, and have found that the values I've chosen happen
correspond to some locally assigned addresses Microsoft have decided to use
(and then globalise) for their MS Network Load Balancer software. I'm not using
any MS software at all in this virtual network.
e.g. in tshark,
--
Ethernet II, Src: MS-NLB-PhysServer-02_00:00:00:01 (02:02:00:00:00:01),
--
I don't think wireshark/tshark should be showing these locally assigned MAC
addresses as being used for a Microsoft product or belonging to Microsoft,
because it's misleading to people who don't know the purpose of the locally
assigned bit/address space.
(I'd hope Microsoft provide a way to change these values - you'd hate to find
that you've, quite rightly, configured these addresses in your network for
something else, and then go to try to introduce MS NLB, and have mac address
collisions. MS should have gone and got their own OUI, and then used addresses
out of that - guaranteeing world wide uniqueness.)
Thanks,
Mark.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
