Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #310 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

Required timestamps, Markdown commands and accepted scripts

  • Clickable video timestamps are required. For each major step taken from the source video, provide the actual MM:SS (or HH:MM:SS) timestamp linked to that exact point in this issue's direct video URL using its t= offset. Map the numbered guide steps and their commands to those timestamps. Label new or changed steps that exist only in the current DragonOS release as current-release additions instead of inventing a source timestamp. Watch and verify the referenced segment; a link to the full video alone is insufficient.
  • Commands must use fenced Markdown code blocks. Use a language tag such as bash for shell commands or python for Python code. Keep commands copyable, omit shell prompt characters, explain placeholders and working directories, and put expected output in separate text or json blocks. Preserve command order and distinguish required commands from optional commands. Screenshots and inline prose supplement the code blocks.
  • Supporting scripts are accepted bounty deliverables. Reusable setup, capture, analysis or verification scripts can be published as public GitLab snippets in Public Repos / irregularchat-snippets, the community's gist-style project. Link each script from the guide and its MR with its filename, purpose, dependencies, inputs, outputs, license/attribution, tested revision/commit when available, and SHA-256 checksum of the tested contents. Include fenced commands to obtain and run the script, example arguments, expected results and cleanup. Record its actual execution on the latest installed DragonOS and map the workflow it automates to the guide/video timestamps. The public script and the wiki guide are parts of this same bounty.
  • Confirm the snippet itself is public. Project visibility alone is insufficient: bot-created snippets default to internal. For a file shared through the Signal bot, its uploader or an admin can reply to the bot's snippet message with the command below. Link the resulting snippet, then verify that its page and source can be read while signed out. Publish only the contributor's intended public code and examples; keep credentials and private captures out of snippets.
!code -p

Acceptance evidence must include the timestamp-to-step mapping, rendered fenced command blocks, and—when submitting scripts—the public snippet URL, tested contents checksum and a reproducible run. Existing latest-installed-DragonOS, topic-specific outcomes and reviewer reproduction requirements still apply.

<!-- dragonos-guide-format-and-scripts:2026-10-18 -->

---

Turn this specific CemaXecuter video into an original, reproducible step-by-step wiki guide tested on the latest installed DragonOS.

Direct source video

DragonOS Focal Remote SDR w/ SDR++, SDRAngel, SigDigger, and Gqrx (Pi4, HackRF, Airspy/HF, RTLSDR) — CemaXecuter. This is the historical source, not evidence that its commands work on the current release.

Who might enjoy this

  • Interest: RF / SDR (Dragon), Tech, hardware, infrastructure.
  • Experience: intermediate. Work style: hands-on. Bounty tier: M.
  • Readiness: needs-device. Prerequisites: Installed latest DragonOS client, a second controlled machine hosting a supported SDR and private lab network access; document the exact SDR++ client/server combination.
  • Skills: docs, qa, shell, hardware. Human installation and execution are required even when an agent helps write the guide.

This guide's bounded deliverables

  • Cover the SDR++ client/server portion of the multi-tool video only. Document starting the current server on a controlled lab machine, connecting the installed DragonOS client and receiving one broadcast test signal.
  • Explain which software runs on each machine, server interface/port, sample-rate/network limits, local firewall scope and how to stop/revert the setup.
  • Keep access on the private lab network; no public port forwarding or shared credentials. Document the actual authentication/encryption behavior without claiming the raw server protocol provides protections it lacks.

Topic-specific acceptance

  • [ ] The client visibly receives samples and demodulates the chosen broadcast signal from the remote radio; record both versions and the source of the samples.
  • [ ] Stopping the server produces an honest disconnected/no-data state; diagnose one endpoint/sample-rate error and restore reception.

Required for every guide in this series

  • Install the latest stable DragonOS x86-64 release, in a VM or on a dedicated machine, and run the exercise there. A live-only session, another Linux distribution, an agent-written transcript, or an unexecuted command list does not meet acceptance. A VM is fine for hardware work only after actual USB/network device access is demonstrated.
  • On2026-10-18, the official files page lists DragonOS Resolute R1 (DragonOS_Resolute_R1.iso, Ubuntu/Lubuntu26.04) as current. Recheck the official release files when starting and before MR review. Record the exact ISO filename, official checksum verification, installed OS release/kernel, relevant application versions, architecture, VM/hardware configuration and test date. If a newer stable release appears, test that release and update the guide. If it breaks the exercise, report the specific blocker instead of silently falling back to Noble/FocalX.
  • Credit CemaXecuter / Aaron, link the direct source video and his channel prominently, and map the relevant video timestamps to the corresponding written steps. Explain which portions of the video this bounded guide covers. Write original explanations and take original screenshots; identify any reused material and its permission/license. A video link is not permission to copy a transcript or redistribute its media.
  • Include a short objective, who the lesson suits, explicit hardware/software prerequisites, expected completion time, numbered steps, copyable commands, explanations of key settings, expected output at each checkpoint, troubleshooting, cleanup and links to primary tool documentation. Annotate screenshots with useful alt text; commands and expected values must also be readable as text.
  • Add a What changed since the video table: old instruction/version, current tested replacement and reason. Verify installed tools before compiling or replacing anything. Use isolated application environments when needed; avoid global pip changes or wholesale SDR-stack upgrades. Never imply an unavailable tool is included in the current ISO.
  • Put the guide under apps/wiki/src/content/docs/radio/ and link it from the existing DragonOS page and the appropriate radio learning page. Follow current wiki conventions. Run the wiki's existing checks/build and report exact results and named baseline failures.
  • Supply a short, sanitized execution log plus original screenshots/artifact checksums. A second reader must reproduce the documented steps on the latest installed release and record the resulting outputs; an agent's assertion is not execution evidence. A Fieldnotes reproduction report may be linked as supplementary evidence, but the deliverable is the reviewed monorepo wiki guide.
  • Use your own, public or permissioned test inputs. State provenance, sample rate/format and license for any recording or dataset committed to the repo; keep large recordings external with a stable source and checksum. Keep credentials, third-party communications, personal device identifiers and precise private locations out of published examples. The SDR receive path stays receive-only; no SDR transmission or production-service access is required. Normal permitted emissions from owned Meshtastic nodes, weather sensors and Remote ID test beacons are part of their controlled tests; state the test setting and applicable device/region configuration.

Repository starting points

Source-reviewed on2026-10-18 against main 8fbef0dc673462283973834b2a753d1b85e61426. Recheck current main, issue discussion and linked MRs before starting.

Contribution and scope

One guide, one independently reviewable MR. Claim/assign the issue and record device access before starting hardware work; move the readiness label to status:in-progress once the prerequisites are met. Device-needed is a prerequisite, not a request for a purchase. Keep software changes to supporting examples essential to this lesson. New services, public listeners, production access, unrelated refactors and bulk dependency upgrades are outside scope. Use this issue's actual number in the MR's closing reference; the existing Scoreboard rules determine eligible points. The series index has no second bounty award.

<!-- dragonos-video-guide:2026-10-18:remote-sdr -->

Series index with every direct video and bounty: #301. Parent community catalog: #258.

Relevant files

No relevant files linked yet.

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top