Nice to have: vendor-lookup for mac-addresses

[hmpf]

Since different vendors have different ranges for their mac-addresses it'd be nice to get the vendor from the mac-address.

Feature breakdown

• Add new database model to store OUI data #2957
• Add maintenance script to download the current official OUI list and insert/update the database OUI model #2958
• Add optional OUI vendor column to Machine tracker MAC searches
• Add new API endpoint to look up OUI vendor from a MAC address
• Create a new NAV cronjob for OUI updater script
• Document NAV's OUI database functionality

[lunkwill42]

A very good compiled list to source for this would be https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob_plain;f=manuf

[olesnhansen]

I would like to see the OUI (https://en.wikipedia.org/wiki/Organizationally_unique_identifier) in NAV -> Machine Tracker-> IP Search/MAC Search.
If NAV could update daily from http://standards.ieee.org/regauth/oui/oui.txt and have an option display the info in the GUI we would have
some idea of the type of equipment behind the address/port.

[renrom]

Is this still actual? i would like this also.

[lunkwill42]

Sure, @renrom. We haven't closed it, because it's a good idea. But we haven't been able to prioritize it thus far.

I guess this would require:

1. A new PostgreSQL table to store the OUI data.
2. A script to download the current list and insert/update the PostgreSQL table.
3. Changes to the Machine tracker MAC search form and result table, with an auxiliary lookup in the new table.

And potentially:

4. A new API endpoint to look up vendors from the PostgreSQL table, so this can be reused elsewhere.

[renrom]

Or a constructed URL to this site? https://macvendors.com/api It should be nice to have a link somewhere if you lookup a client device IP/Mac Address to this url https://api.macvendors.com/

[lunkwill42]

Or a constructed URL to this site? https://macvendors.com/api It should be nice to have a link somewhere if you lookup a client device IP/Mac Address to this url https://api.macvendors.com/

That would have to be a very explicit and manually invoked link per displayed MAC-address. Automatically dumping a bunch of potentially private data into a 3rd party website won't be everyone's cup of tea...