ados-macpin
Stable MAC addresses for Linux network adapters that randomize theirs every boot: chipset quirk table, deterministic per-machine derivation and systemd-networkd .link files.
Some USB WiFi chipsets have no MAC burned into efuse, so their driver invents a new random address each time it loads. On a DHCP network that means a new lease and a new IP every boot, which makes the machine hard to find. This crate pins a stable, locally administered MAC derived from /etc/machine-id, written as a systemd-networkd .link drop-in that takes effect on the next boot without touching the live interface. Reach for it on any embedded Linux box with a randomizing adapter.
use PathBuf;
use ;
use ;
// An AIC8800-family USB WiFi adapter: a known randomizer.
let id = UsbId ;
assert!;
// Same machine-id and USB port in, same MAC out, on every boot.
let mac = derive_pinned_mac.unwrap;
assert!;
let layout = PinLayout ;
let key = adapter_key;
let name = link_file_name;
let body = render_link_file;
assert_eq!;
assert!;
assert!;
Highlights
- Deterministic: the MAC is
02:plus five bytes ofsha256(machine_id:salt), so it is stable per machine and distinct across machines and USB ports. - Refuses unsafe
.linkfiles: a[Match]block that does not name exactly one adapter (a glob, a negation, a bareDriver=) is rejected before anything is written. - Next-boot only: provisioning writes a file and reloads the udev rules database; it never runs
udevadm triggeron thenetsubsystem and never changes a live address unless you callapply_live. - Every path is yours: the state file, drop-in directory, file prefix and header label come from a
PinLayout. - A cross-boot learner flags unknown adapters whose MAC keeps changing, for an operator to confirm.
- Async entry points (
apply_live,remove_pin_link) runipandudevadmbounded undertokio::processwithkill_on_drop.
How it works
Detection does not trust two signals that look authoritative but lie in practice: the kernel's addr_assign_type can read 0 (permanent) while the adapter randomizes, and the random MAC can carry a real-looking vendor OUI with the locally administered bit clear. So randomization is identified by chipset VID:PID (MAC_QUIRKS) or by observing the MAC change across boots for a stable device identity. Chipsets in KNOWN_STABLE_EFUSE are never pinned.
An adapter is identified by its model plus the USB port it sits in (adapter_key, vvvv:pppp@<usb_path>), which survives kernel renames and enumeration-order changes. classify_adapter is the pure decision: an operator override wins, then the stable-efuse allowlist, then the quirk table (pin when enabled, a systemd-udev link mechanism exists and a machine-id is available), then the learner (a candidate after LEARN_THRESHOLD MAC changes).
The .link file matches on the adapter's udev ID_PATH (Path=), sets NamePolicy=kernel so the interface keeps its name, and sets an explicit MACAddress=. That key is unconditional, which is why match_block_is_specific guards every write: a wildcard match would hand one address to every interface on the machine.
On Linux, reconcile runs the whole pass: enumerate /sys/class/net, fold the learner, classify, write or sweep .link files and persist a MacPinsState JSON document atomically. On other platforms the sysfs functions are stubs, so the pure logic builds and tests anywhere. The engine module also has helpers that project the state file to camelCase JSON for a status API.
Part of ADOS
Used in production by the ADOS Drone Agent, the onboard software of the ADOS software-defined drone platform. All ADOS crates · Docs · Discord
Other ADOS crates
Platform (versioned with the ADOS Drone Agent)
| Crate | What it does | Docs |
|---|---|---|
ados-protocol |
Wire contracts of the ADOS Drone Agent: IPC framing, plugin RPC envelope, capability tokens and the vision frame bus. | docs.rs |
ados-sdk |
Write Rust plugins for the ADOS Drone Agent: IPC client, plugin context, driver traits and lifecycle runner. | docs.rs |
ados-vision |
Single-object visual tracker: Kalman motion model, appearance re-identification and YOLOv8 head decoding. | docs.rs |
ados-gpio |
Drive status buzzers and LEDs on Linux GPIO lines, with bounded software-PWM beep patterns. | docs.rs |
ados-hal-probe |
Find out what a board's hardware can really do by probing it, plus bundled board profiles. | docs.rs |
Standalone
| Crate | What it does | Docs |
|---|---|---|
ados-sensorhub |
Sensor hub wire protocol: COBS framing, CRC-16 and fixed-layout IMU, baro, mag and GNSS packets. no_std. | docs.rs |
ados-offload |
Choose where perception runs (onboard, offloaded or hybrid) and hold the vehicle when results go stale. | docs.rs |
ados-lora |
LoRa transmit governor with cited regional band plans, duty cycle, dwell time and airtime accounting. | docs.rs |
ados-crsf-codec |
no_std CRSF / ExpressLRS codec for RC channels, telemetry and parameter frames. | docs.rs |
ados-positioning |
Split mixed UBX, NMEA and RTCM3 GNSS streams, configure u-blox receivers and run an RTK base survey-in. | docs.rs |
ados-rtcm |
RTCM3 framing, CRC-24Q and MAVLink GPS_RTCM_DATA fragmentation for RTK corrections. | docs.rs |
ados-clock |
Map remote clocks onto the host clock: least-squares and envelope fits, TIMESYNC and a chrony sink. | docs.rs |
ados-swarm |
Swarm control laws: separation, flocking, formations, CBBA task allocation and a point-mass simulator. | docs.rs |
ados-mavlink-tunnel |
Send large messages over MAVLink TUNNEL frames with chunking and bounded reassembly. | docs.rs |
ados-display-driver |
Small-display output on Linux: SSD1306/SH1106 OLED over I2C, pixel packers and a framebuffer writer. | docs.rs |
ados-hmi |
Front-panel input: touchscreen calibration and gestures, button presses and rotary encoders. | docs.rs |
ADOS repositories
| Repo | Runs on | What it does | Link |
|---|---|---|---|
| ADOS Mission Control | Browser, desktop (Electron) | Ground control station: FC setup, mission planning, flight, 3D simulation, fleet | ADOSMissionControl |
| ADOS Drone Agent | Companion computer on the drone, or a ground node | Onboard agent: MAVLink routing, HD video, long-range radio link, plugins, remote control | ADOSDroneAgent |
| ADOS Android GCS | Android phones and tablets | Native ground control app for agents on the LAN, direct flight controllers and the cloud | ADOSAndroidGCS |
| ADOS Extensions | Drone Agent and Mission Control | First-party signed plugins, each with an agent half and a GCS half | ADOSExtensions |
| ADOS MCP | Your machine | Model Context Protocol server that lets AI clients operate ADOS drones under scopes and a safety gate | ADOS-MCP |
| Documentation | docs.altnautica.com | Public docs for every ADOS product | Documentation |
License
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.