| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Checked the actual upstream diffs, not just PR titles: #359/#370's
identity-validation changes only add collision checks between multiple
identities configured on one node (repeater/companion/room-server sharing
a one-byte prefix namespace), unrelated to the single-identity load path.
config.py's _load_or_create_identity_key is unchanged in 1.1.4 and still
silently generates a fresh identity on any read failure instead of
failing loudly, same mechanism as the 2026-08-10 stale-UID incident. Not
introduced or fixed by this bump, so nothing blocks it, but the
underlying fragility remains latent upstream.
|
|
Reword the lookup comment above each upstream _version var to a single
greppable "# version-check: <url>" marker, always placed directly above
the version line, so a script can find every instance with one grep.
Bump bin 2.0.1 -> 2.0.2, pleroma 2.10.0 -> 2.11.0, relayer 2.2.8 -> 2.3.1,
ergo 2.18.0 -> 2.19.1, openhop_repeater 1.1.1 -> 1.1.4, keeping the
bin/server and pleroma/otp duplicate version vars in sync.
Add a TODO on openhop/repeater to review upstream's identity-validation
changes (1.1.2-1.1.4) against the stale-UID bug before deploying to the
live mesh node.
Document the version-check convention in the README.
|
|
- create spi/gpio groups and udev device rules (Raspberry Pi OS ships them, Ubuntu does not)
- hardware CS via spidev (cs_pin -1); a manual cs_pin on a kernel-owned CE line fails EBUSY
- align RAK6421 pin maps with upstream's hardware catalog: en_pins for the FEM enables,
gpiod backend on chip 0 (catalog says chip 1, wrong for Pi 4)
- us RF preset is now MeshCore USA/Canada (Recommended): 910.525 / SF7 / BW62.5 / CR5
- set storage.storage_dir; omit mqtt_brokers entirely (any key enables the MQTT pusher)
- fetch radio-settings/radio-presets json into the data dir (pip omits them and the web
setup wizard's hardware step is empty without them)
- config deployed 0660 with a vaultable repeater.security block so the daemon can persist
credentials and re-templates no longer wipe them
- sudoers rule so the web UI can restart the service after config changes
|
|
Deploys the openHop MeshCore repeater on a Raspberry Pi with a RAK6421
WisMesh Pi HAT: installs the daemon into a venv from a versioned git tag,
templates config.yaml and a systemd unit, and loads board pin maps and RF
region presets by name from vars/. identity_file is configurable and
defaults to null (daemon generates its own keypair).
|
