Line 4 for the local location to output the OUI List too.The resulting object looks like this: vendor base16 hex This little script will download the latest version of the OUI list and convert to a PowerShell Object. Converting the IEEE List to a PowerShell Object The full list to too large to keep locally so I exported the full list (again using export-clixml) and implemented a lookup as an Azure Function (that reads in the full list as a PSObject that takes ~1.7 seconds for 25,000+ records) which can then be queried with either Hex or Base16 as per the format in the IEEE list and the vendor name is returned. I then extracted the manufacturers I expect to need to reference/lookup into a PSObject that is easily exportable and importable (export-clixml / import-clixml) and use that locally in my application. I downloaded this list and wrote a simple parser that created a PowerShell Object with the Hex, Base16 and Name of each Manufacturer. A full list can be found here which is updated regularly. The IEEE standards body maintains a list of the manufacturers assigned the 24 bit identifiers. So I rolled my own using an Azure Trigger Function. I needed more than 1000 per day, but I also had a good idea of what the vendors were likely to be for a lot of my requests. If you are only looking up small volumes that is all good, but after that you get into subscription fee costs. And some like that one have an API to allow lookup too. There are a number of online lookup tools to determine who the vendor is from the MAC address. A MAC Address looks like this 60:5b:b4:f9:63:05. The first 24 bits (6 hex characters) detail the vendor / manufacturer. As you are probably aware each network device has a unique MAC Address.
As part of that I needed to identify the Vendor / Manufacturer of networking equipment. Recently I started working on another side IoT Project.
0 kommentar(er)
