Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] URL and encoding for OUI listings in make-manuf

From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Tue, 17 Jun 2008 21:02:38 +0200
Hi,

Indeed this new link is the updated list. The old one seems stale.
Also the UTF-8 stuff needs to get sorted. Please file a bugreport so it won't be forgotten.

Thanx,
Jaap

Thomas Boehne wrote:
Hi,

we have bought a new MAC address range from IEEE and I was just
checking if it shows up properly in wireshark -- it does not. The
make-manuf script uses this link:

http://standards.ieee.org/regauth/oui/oui_public.txt

which seems to be outdated. The link that is on their website at
http://standards.ieee.org/regauth/oui/index.shtml

points to http://standards.ieee.org/regauth/oui/oui.txt
which seems to be updated regularly, and seems to have the same format
as the old file. I suggest we use the new link in make-manuf.

Another bug that I discovered is that non-ASCII characters in the
company name create problems. E.g., the name "Jäger Computergesteuerte
Messtechnik" gets abbreviated to "J?GerCom" where it should be
"JägerCo", and wireshark displays the follwing warning:

(wireshark:17282): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

After downloading the oui.txt file manually and converting it to utf-8
with iconv, the warning was gone. Is there a perl expert who can do
the conversion in the make-manuf out there? I guess it would be the
right place to do it.
Another small problem with make-manuf is the line

$manuf =~ s/(\w+)/\u\L$1/g;

which creates an uppercase character after special characters, e.g.
JäGerComp instead of JägerComp.

Should I create bugzilla entries for those minor issues?

Best regards
Thomas Böhne