Skip to content

Synthetic example profile

Fresh installation requires a reviewed private --profile-dir; normal upgrades preserve installed hardware settings. See hardware profile selection.

Synthetic hardware example: serials and antenna labels below are examples. Retained topology/model relationships do not qualify replacement equipment. Customize a private copy and select it explicitly for a fresh installation.

The network identity in etc/rfsentry/appliance.conf.example is synthetic. Customize its reserved example hostnames, addresses and certificate-issuance policy before use. Keep actual recovery identity in private operator storage. The directory name is a stable hardware-profile selector, not a network alias. This synthetic template illustrates a Raspberry Pi 5 and a two-tier USB hub. Verify topology, device capabilities and policy against your own hardware.

Hardware topology reference

  • Raspberry Pi 5 Model B Rev 1.1, Raspberry Pi OS / Debian Trixie, ARM64.
  • An externally powered StarTech ST7300USB3B two-tier VIA VL813 hub.
  • Pi USB2 root hub 3 (1d6b:0002) feeds the primary tier at 3-1 (2109:2813), then the leaf tier at 3-1.1 (2109:2813).
  • USB3 companions are 4, 4-1, and 4-1.1; uhubctl handles the companions.
  • Only root hub 3 port 1 is managed. Other Pi USB ports/controllers are not included in this profile's shutdown policy.
  • Primary port 1 is the internal cascade: reserved, never directly switched. Primary logical ports 2/3/4 remain physical panel ports 5/6/7.
  • Leaf logical ports 1/2/3/4 remain physical panel ports 1/2/3/4.
pi_usb                3        managed upstream port 1
  startech_primary    3-1      reserved cascade port 1; user ports 2-4
    startech_leaf     3-1.1    receiver ports 1-4
Leaf/panel port Receiver alias Example serial Public / backend TCP
1 hf_receiver 90000001 1234 / 11234
2 vhf_ant 90000002 1235 / 11235
3 adsb1 90000003 1236 / 11236
4 satcom1 90000004 1237 / 11237

The Ham It Up remains a power-only accessory on primary logical port 4 / physical panel port 7. It has no discoverable USB serial of its own.

Receiver serials, aliases, antenna descriptions, public/backend ports, and verified route ranges illustrate the retained hardware relationships. The HF upconverter translation remains 125 MHz. SATCOM retains the verified E4000 low/high ranges and tuning gap. Discovery always verifies serials; a port number is not receiver identity. The runtime port-map cache is intentionally not included.

The externally powered hub uses logical USB isolation; do not interpret port state as proof that power-only loads lose VBUS. The Pi root is also configured as logical-only. Verify actual switching behavior on your hardware rather than inferring it from hub descriptors.

Recovery and upgrades

Inspect the USB topology again if this hub moves to another Pi socket:

hostnamectl
lsusb
lsusb -t
sudo uhubctl
./install.sh --check --profile example

For a fresh installation, copy/edit the synthetic etc/rfsentry/appliance.conf.example into ignored config/local/appliance.conf and explicitly supply it:

sudo ./install.sh --install --profile-dir config/local/hardware-profile \
  --appliance-config config/local/appliance.conf

For a normal upgrade, schedule a maintenance window. The installer validates and uses the existing hardware configuration and appliance identity:

sudo ./install.sh --install

A full install warns about active clients and proceeds, interrupting acquisition. Saved enabled jobs resume when services start. Interactive clients must reconnect. --no-start leaves services stopped after installation. Use --check to inspect the profile without installing it.

The profile includes client-only Chrony, existing demand/idle deadlines, automatic network-interface/gateway discovery, bounded health recovery, propagation-cache policy, and Video/AF41 IQ QoS on the configured stream port. It includes the model-independent ramoops reservation but no Pi 4 voltage fragment and no overclock/voltage override. Health and watchdog behavior are explicit policy in etc/sdr-health.conf; review them before an installation.

Hostnames and public aliases appear only in the explicit identity example; they are not compiled into component defaults. TLS keys/certificates, tokens, Wi-Fi profiles, SSH keys, client recordings, and live caches are not included.