Services: Kea DHCP: Leases DHCPv4 Not showing recent registered vendor

Started by hazuki, August 13, 2025, 02:51:17 AM

Previous topic - Next topic
Hi,

In the DHCP lease table of (Web UI) Services: Kea DHCP: Leases DHCPv4, MAC address column shows vendor information if the database in somewhere has such information.

I do believe above-mentioned database is pretty much outdated as the table does not show the vendor information of some of my devices (e.g. D8:3B:DA, 10:00:3B, 5C:01:3B), which upon checking, the OUI was registered in 2024.

I want to update the database (if the database is within the metal) or update the link to the database (if the database is on the internet). Where should I start from? Any help is appreciated.


Thanks in advance,
Hazuki



Thanks @RamSense!

So the answer to my question is basically in https://github.com/opnsense/core/issues/5205
#! /bin/sh
cd /usr/local/lib/python3.8/site-packages/netaddr/eui
curl -s -o oui.txt https://standards-oui.ieee.org/oui/oui.txt
curl -s -o iab.txt https://standards-oui.ieee.org/iab/iab.txt
python3 ieee.py

By the way, I do think we should not rely on the generated files from https://github.com/netaddr/netaddr/blob/master/netaddr/eui/iab.idx and https://github.com/netaddr/netaddr/blob/master/netaddr/eui/oui.idx. The script ieee.py still works as at today and I don't think the author is obligated to update these files in github/upstream as developers using his code shall generate the files on his own.

My 2 cents,
Hazuki

correct, although this depends on what version of OPNsense you are running. It is now python3.11
so you should change the location to : cd /usr/local/lib/python3.11/site-packages/netaddr/eui
Deciso DEC850v2

The release notes for 25.7.4 details:

o interfaces: replace MAC vendor database from py-netaddr with a simple local implementation

Is there a mechanism to manually update the MAC vendor database or is it updated periodically / automatically?

The OUI database is included in the OPNsense core package. As far as I'm aware, the only intended way of updating it is updating OPNsense itself.

Cheers
Maurice
OPNsense virtual machine images
OPNsense aarch64 firmware repository

Commercial support & engineering available. PM for details (en / de).

Correct. I don't mind pulling an update, but not for every minor release for a single line change. It's also possible to update locally by replacing the input file I guess although it will show in the health audit for the right reasons.


Cheers,
Franco