Wireshark OUI Lookup Tool Broken

edit

Can you provide some examples that don't work?

Some recent work was done on the tool, so I would expect it to be working better than it had before. See Bug 16038.

Example: 00d9.d110.21f9 No Matches

Example: 00:d9:d1:10:21:f9 00:D9:D1 Sony Interactive Entertainment Inc.

These formats all work:

OUI search           Results
00:d9:d1             00:D9:D1 Sony Interactive Entertainment Inc.
00-d9-d1             00:D9:D1 Sony Interactive Entertainment Inc.
00.d9.d1             00:D9:D1 Sony Interactive Entertainment Inc.
00:d9:d1:10:21:f9    00:D9:D1 Sony Interactive Entertainment Inc.
00-d9-d1-10-21-f9    00:D9:D1 Sony Interactive Entertainment Inc.
00.d9.d1.10.21.f9    00:D9:D1 Sony Interactive Entertainment Inc.

Can you please try this format (format of any Cisco device, and #1 on the example list): 6412.25e4.2d62

Sorry, I didn't mean to imply that all formats worked, only those formats that I listed. The bug I linked to refers to the recent work done on the OUI tool, and apparently not every format is supported, whether by omission or by design. The example on the OUI lookup page works, namely 0000.0c, and so does 6412.25, but other formats don't work as you've discovered. I'd recommend adding a comment to the bug report asking about this, and then either someone (Peter, most likely) can either explain why it's not supported or reopen the bug to fix the tool.

Will do! Thanks for your reply, sorry for the confusion. I would imagine that this is the most popular format for the tool.

I'll restore support for other formats. It was removed because these were not documented as valid options and the old parser was overly permissive. You can follow progress in the bug linked by Guy below.

Awesome! I was just curious as that format is the first in the examples and widely used. Glad to hear it's getting fixed!

48d6-d5e2-a67c Is another popular format (HP) that is also not supported by the lookup tool.

A fix has been implemented and deployed, thanks for raising this!

This site seems to provide better results for its lookup tool: https://aruljohn.com/mac.pl. It doesn't care how many octets you supply, nor does it care what the byte separator is (even this works: 48*D6&D5^E2@A6), or how the bytes are grouped.