Register a Bluetooth SIG Company Identifier

Christian Marangi (Ansuel) ansuelsmth at gmail.com
Tue Aug 11 02:17:25 PDT 2026


Il giorno mar 11 ago 2026 alle ore 03:00 Eric
<evil.function at proton.me> ha scritto:
>
> And there's also the PEN, useful for DUID-EN, and extending SNMP, LDAP...
>
> OpenWrt's IANA-assigned Private Enterprise Number (PEN) is 39482.
> OpenWrt's OUI prefix is 20:05:b6
>
> We ought to put them in the wiki somewhere...
>

I think the OUI is already documented...

May I ask where does PEN number comes from? Inspecting it, it's a provate
company [1]

[1] https://www.iana.org/assignments/enterprise-numbers/?q=39482

> Eric
>
> On Monday, August 10th, 2026 at 13:00, John Crispin <john at phrozen.org> wrote:
> > Hi Mathias,
> >
> >  > Can you elaborate about the pros for the OpenWrt eco-system?
> >
> > I have been playing with BT/LE USB dongles on an OpenWrt One, trying to
> > get GATT/GAP working without dragging in bluez and dbus using
> > ucode-mod-bluetooth. Advertising
> > anything of our own needs an ID that only the SIG hands out, same deal
> > as the OUI range we registered with the IEEE.
> >
> >      John
> >
> > On 09.08.26 08:55, Mathias Mahnke wrote:
> > > Hi John,
> > >
> > > * 08.08.26 16:32 John Crispin:
> > >> Hi all,
> > >>
> > >> OpenWrt should register a Bluetooth SIG Company Identifier. It gives
> > >> the project its own allocated ID for use in BLE. One-off fee is $1250
> > >> at the Adopter tier, paid through SFC, and they'd handle the
> > >> registration for us. This doesn't need a full [VOTE]. If nobody
> > >> objects in the next three days, the project will ask SFC to go ahead.
> > >
> > > many thanks for bringing this registration process here into
> > > attention. Can you elaborate about the pros for the OpenWrt eco-system?
> > >
> > > If found some reference docs:
> > > <https://support.bluetooth.com/hc/en-us/articles/360062030092-Requesting-Assigned-Numbers>
> > >
> > > <https://support.bluetooth.com/hc/en-us/articles/19287261092109-Company-ID-Questions>
> > >
> > >
> > > Should we use it for the OpenWrt hardware or is this an solution for
> > > the software stack itself (running on all owrt supported HW)?
> > >
> > > And: No objections here from my end. Just a request for information.
> > >
> > > Best,
> > > -mathias
> > >
> > >
> > > _______________________________________________
> > > openwrt-adm mailing list
> > > openwrt-adm at lists.openwrt.org
> > > https://lists.openwrt.org/mailman/listinfo/openwrt-adm
> >
> >
> > _______________________________________________
> > openwrt-adm mailing list
> > openwrt-adm at lists.openwrt.org
> > https://lists.openwrt.org/mailman/listinfo/openwrt-adm
> >
>
> _______________________________________________
> openwrt-adm mailing list
> openwrt-adm at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-adm



More information about the openwrt-adm mailing list