silverwind/oui

CLI to look up MAC addresses for their vendor in the IEEE OUI database

oui

CLI to look up MAC addresses for their vendor in the IEEE OUI database

Note: This module is CLI only since v13. The data has moved to module oui-data.

Usage

$ npm i -g oui
$ oui 20:37:06:12:34:56
Cisco Systems, Inc
80 West Tasman Drive
San Jose CA 94568
United States

© silverwind, distributed under BSD licence

oui's Issues

Update the update mechanism

Looks like the IEEE website changed, and the oui.txt file is not available anymore. The new format seems to be either text or csv, thought the format on the text file has changed, so I'll be switching over to parsing the csv at:

https://services13.ieee.org/RST/standards-ra-web/rest/assignments/download/?registry=MA-L

Missing Package Updates

Hi,

This package used to get weekly updates with data, but these seem to have stopped, with the last being April 4th.

Is there an issue with the CI/CD pipeline maybe?

Reverse lookup

I think I'll implement this as a simple search for a provided string.

Add tests

Support IABs (Individual Address Block)

http://standards-oui.ieee.org/iab/iab.txt

http://standards.ieee.org/faqs/regauth.html#20
https://en.wikipedia.org/wiki/Organizationally_unique_identifier#Individual_Address_Block

Support zero-truncated MACs

NPM audit reports MitM vulnerability on [email protected]

The error i'm getting is that: https-proxy-agent is the root cause.
The chain of its usage is: oui > make-fetch-happen > https-proxy-agent

make-fetch-happen has updated its https-proxy-agent dependency to fix this security issue: npm/make-fetch-happen@2141605

Change to IEEE source and fix broken ASCII

See a5962b8#commitcomment-33639537. The IEEE source has broken upper 8-bit ASCII characters. A attempt could be made to fix this by running the text through iconv-lite or similar.

Move all dependencies to devDeps

I think the update feature could be seperated from the main export, like for port-numbers.

Problem with using mulitple JSON dbs

As demonstrated, this works well. However, I want to use different JSON files to find information based on the OUI portion of mac address. Specifically, I have 3 classes: Supported Manufacturers, Probably conformant manufacturers, and all other manufacturers. THe oui.json file fits the bill for the last category. However, I have created separate JSON files for my supported manufacturers (i.e. I've verified against)
containing their OUIs and another file that contains the OUIs of the manufacturers that purport to support the software I'm trying to use, but I've not personally tested against it.

Once a JSON db is loaded, then using the file option does not work. It re-uses the previous JSON file. I believe a change as follows will fix it:
const oui = module.exports = function oui(input, opts) {
if (typeof input !== "string") {
throw new Error("Input not a string");
}

opts = Object.assign({}, opts);

if (opts.file || !db) { // CHECK IF HE HAS SPECIFIED A NEW DB
db = require(opts.file || "./oui.json");
}

Stdin support

echo 012345 | oui should be supported.

Sync API

The async callback with the result is unnecessary, and I plan to move the lookup api to purely sync functionality in 3.0. The update will of course stay async.

update() method too slow.

The update() method is really but really slow.
That oui.txt file is not even provided from a CDN... and seems to be "streamed".

Perhaps is better to use wireshark's one?
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob_plain;f=manuf

MAC Randomization

It is my understanding that if the first octet ends in 2, 6, a, or e, then the MAC address has been randomized. It is also my understanding that the entire MAC address is random, including the three OUI octets.

Is it possible to return some sort of indication that a MAC address is not being controlled by an OUI or manufacturer?

Browser compatibility

Using this module with any modern bundler (e.g. vite) breaks it.