<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>DragonOS FocalX RedHawk Domain Manager Setup w/ Remote RTLSDR Client (RTLSDR v3, Docker)</title>
        <link>https://stream.echo6.co/videos/watch/5733b72d-4550-454d-8cce-869e5900390d</link>
        <description>"REDHAWK is a software-defined radio (SDR) framework designed to support the development, deployment, and management of real-time software radio applications." https://redhawksdr.org/2.2.5/getting-started/ With that in mind, this video covers how to setup the RedHawk 2.2.5 (newest docker available, but not the newest RedHawk) domain manager on DragonOS FocalX using Docker. You'll also see how a second system with the same setup plus RTLSDR communicates back to the domain controller. Hopefully I'll get around to more research on RedHawk. It seems to have an interesting history, but honestly the documentation/setup may be something I'll just have to build on as time permits. A few things about the setup shown in the video. I notice that log4j appears in the 2.2.X RedHawk w/ the 3.x version mentioning log4j being replaced by reload4j, so keep that in mind in terms of vulnerabilities, I’ve not looked into it much. I installed docker-compose even though "docker compose" was actually available after installing docker from the offical repository. Turns out the way I did it in the video avoids a warning about the "redhawk_sdrroot volume already existing but was not created by Docker Compose". After setting up the .env with the HOSTNAME, you should run source .env in the terminal before proceeding with docker-compose commands. That will make those environmental variables available and will fill in the $HOSTNAME, etc. I also had issues with the IDE script that's supposed to open it. Instead I found that running it directly in terminal worked, notice I changed the workspace location. Which this reminds me, I didn't create the workspace directory in the video. You can create it where you'd like, but I should've ran mkdir /home/dragon/workspace for example. sudo docker run --rm -d -e RHUSER_ID=$(id -u) -e OMNISERVICEIP=$HOSTNAME -e DISPLAY=$DISPLAY -v redhawk_sdrroot:/var/redhawk/sdr -v /home/dragon/workspace -v /tmp.X11-unix/tmp/.X11-unix -P --network host --name redhawk_development_1 geontech/redhawk-development:${RH_VERSION} By the end of the docker setup you should be able to run the RTLSDR script either locally or remotely. In my case I was running one instance of DragonOS FocalX in a virtual machine and for whatever reason during the video wasn't getting the RTLSDR passed through. I switched to my host DragonOS FocalX which had the same setup steps performed on it and used it to share the RTLSDR over the network to the RedHawk domain controller. Follow @cemaxecuter on Twitter for more DragonOS and SDR info. Become a patron @ https://www.patreon.com/cemaxecuter</description>
        <lastBuildDate>Sun, 26 Apr 2026 16:19:04 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://stream.echo6.co</generator>
        <image>
            <title>DragonOS FocalX RedHawk Domain Manager Setup w/ Remote RTLSDR Client (RTLSDR v3, Docker)</title>
            <url>https://stream.echo6.co/client/assets/images/icons/icon-512x512.png</url>
            <link>https://stream.echo6.co/videos/watch/5733b72d-4550-454d-8cce-869e5900390d</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://stream.echo6.co/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://stream.echo6.co/feeds/video-comments.xml?videoId=5733b72d-4550-454d-8cce-869e5900390d" rel="self" type="application/rss+xml"/>
    </channel>
</rss>