This can be used to start bootmac reliably (in my limited testing), the
1 second delay seems to be enough for the hw to be ready for setting the
mac addr. There are probably better ways to do this.

Being part of the bluetooth.target means that this service (if
enabled) is started automatically every time the bluetooth service is
(re)started. It's functionally the same as starting bootmac via udev,
except we can easily add delays in this unit file (while delaying udev
rule execution is... dice-y)

The udev rule for bluetooth doesn't work on systemd[1], by splitting the
rule into two separate rules, distros can leave this bluetooth rule out
when packaging for systemd.

Distros packaging bootmac will have to make note of the new rule
files/names.

1. https://github.com/systemd/systemd/issues/35003

add mandatory parameter checking for right format of if-name and bytes

Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>

use case: overwrite the default host address already set. In this case the
bt host is already up but needs the new address.

Signed-off-by: Jens Glathe <jglathe@oldschoolsolutions.biz>

parameter for variable static prefix

Signed-off-by: Jens Glathe <jglathe@oldschoolsolutions.biz>

In this mode bootmac prints the derived MAC value for either Bluetooth
or Wi-Fi, but does not actually configure the hardware.

Hardcoding all possible argument values is not feasible for more than
2 options, since there will be N! (N factorial) possible options.

Syboxez Blank authored 1 year ago and Dylan Van Assche committed 1 year ago

This allows for more granular service enablement and ordering,
along with enabling the ability to configure MAC post-boot.

Thanks to @NekoCWD for the workaround.
Fixes: https://gitlab.com/postmarketOS/bootmac/-/issues/3

Something must have gone wrong with the previous commit

Be compatible with any POSIX shell

Run shellcheck on every merge request.

Manufacturer OUI lookup is removed

Read rfkill state of Bluetooth and WLAN interfaces before setting
the MAC address. After setting the MAC address, restore the saved
rfkill state.

Fixes https://gitlab.com/postmarketOS/bootmac/-/issues/2

qmac was renamed to bootmac

Use 02:00 to specify that we generate a local administered
address as MAC address. This approach is used by all MSM8916 devices.

Fixes https://gitlab.com/postmarketOS/bootmac/-/issues/1

qmac was renamed too bootmac

Bootmac configures the MAC addresses of WLAN and Bluetooth interfaces at boot.
Bootmac can be invoked in various ways at boot, but currently only udev rules are tested.
Bootmac generates MAC addresses from the `serialno` provided by Android bootloaders
through /proc/cmdline or from /etc/machine-id. The Organizationally Unique Identifier (OUI)
is retrieved from a lookup database macdb by matching deviceinfo_manufacturer
from /etc/deviceinfo with the entries in the database.