Skip to main content

[EN] Linux — ADS-B.Pro feeder installation

This guide is for Raspberry Pi and other Linux computers. Supported architectures are amd64, arm64, armv6, and armv7.

The new feeder connects to ADS-B.Pro Feederover Setupencrypted GuideTLS. Your token is needed only for the first pairing of an installation — it is not sent with every ADS-B frame.

1.Before Requirementsyou start

You will need:

  • Raspberryan PiADS-B.Pro /account Debianand /a Ubuntutoken beginning with internet access.ADS-;
  • RTL-SDRa or anotherworking ADS-B receiver.data source on the same machine;
  • Workingan account with dump1090-fasudo, access;
outbound access to dump1090-mutabilityfeed.ads-b.pro on port 48582.

The installer looks for valid frames, not for particular program names:

    Beast Binary on 127.0.0.1:30005; if no valid Beast frame is received within 5 seconds — BaseStation/SBS on 127.0.0.1:30003.

    This works with readsb, dump1090, or readsbtar1090.

    ADS-B.Pro account. Your private feeder token.

    The feeder token is unique per account. In the account panel it is shown as Your Feeder Token, and hasother thissoftware format:exposing a compatible stream.

    Installation

    Run in a terminal:

    ADS-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    That means ADS- plus 32 hexadecimal characters. The setup script expects lowercase a-f.

    2. Where To Find Your Token

      Log in to ADS-B.Pro. Open My Account. Copy the value from Your Feeder Token. Do not publish this token in logs, screenshots, GitHub issues, or config examples.

      The frontend displays this token from your account data. The actual feeder sends it to the backend through /opt/radarview.py.

      Use radarview_setup-nogit.sh. It does not require cloning the repository and downloads the current radarview.py automatically.

      sudo apt update
sudo apt install -y curl wget ca-certificates

curl -fsSL https://raw.githubusercontent.com/br3jski/radarview/refs/heads/main/radarview_setup-nogit.radarview_setup.sh -o radarview_setup-nogit.sh
chmod +x radarview_setup-nogit.sh| sudo ./radarview_setup-nogit.shbash

      TheIf scriptno willprevious askconfiguration is found, the installer asks for your token:

      Please enter your RadarViewADS-B.Pro token (format:without displaying it on screen.

      The installer:

        downloads the correct feeder build for the computer; verifies the signed release manifest and the file's SHA-256 checksum; creates the dedicated adsbpro-feeder system user; stores the installation's private key locally only; installs and starts a hardened systemd service; enables the local status page on port 54321; waits for the connection and the first frame accepted by ADS-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX):B.Pro.

        PasteThe temporary token copy is removed after successful pairing.

        Migrating from /opt/radarview.py

        Do not remove the old radarview service before installation.

        The installer can read the token from Mythe Account.

        old

        4.script Whatwithout Theprinting Scriptit. Does

        It

        The script:

          Checks that it is running as root. Validatesdisables the userold token. Checks whether a local ADS-B source exists:
            dump1090-fa dump1090-mutability dump1090 readsb If no dump1090/readsb installation is found, it asks whether to install dump1090-fa. Downloads radarview.py to: 
            /opt/radarview.py
              Inserts your token into: 
              USER_TOKEN = 'ADS-...'
                Creates a systemd service: 
                /etc/systemd/system/radarview.service
                only
                  Starts and enablesafter the service:new 
                  systemctl start radarview
systemctl enable radarview

                  5. How Data Forwarding Works

                  radarview.pyfeeder connects to yourADS-B.Pro localand ADS-Bsends receiverits first accepted frame. The old script stays on disk for emergency rollback.

                  Do not run both the SBS/BaseStationlegacy port:and the new feeder for the same receiver. That sends duplicate data and wastes bandwidth.

                  Verify the installation

                  Feeder status:

                  127.0.0.1:30003sudo /usr/local/bin/adsbpro-feeder status

                  ThenService itstatus forwardsand therecent data to ADS-B.Pro:

                  feed.ads-b.pro:48581

                  Before every aircraft data line, the script sends your token:

                  TOKEN:ADS-...

                  So two things are required:

                    local dump1090 / readsb must expose SBS data on 127.0.0.1:30003, the feeder machine must be able to make an outbound TCP connection to feed.ads-b.pro:48581.

                    6. Verify The Installation

                    Check service status:logs:

                    sudo systemctl status radarviewadsbpro-feeder --no-pager
sudo journalctl -u adsbpro-feeder -n 50 --no-pager

                    WatchStatus live logs:page:

                    http://FEEDER-IP-ADDRESS:54321

                    On the same machine use http://localhost:54321. The status port is intended for your LAN or VPN only — do not expose it to the Internet with router port forwarding.

                    The expected state is ACTIVE. The page also shows aircraft count, message rate, current upload rate, and feeder version.

                    Adding another installation to the same account

                    The first v2 installation can be paired with the token alone. Before pairing every additional installation, open a 10-minute pairing window in your ADS-B.Pro account and then run the installer on the new computer.

                    Non-standard source address or port

                    For a source running on a different host or port, download the setup script and pass explicit options, for example:

                    curl -fsSL https://raw.githubusercontent.com/br3jski/radarview/main/radarview_setup.sh -o /tmp/radarview_setup.sh
sudo bash /tmp/radarview_setup.sh --source-host 192.168.1.25 --source-mode beast --beast-port 30005

                    For BaseStation/SBS use --source-mode sbs --sbs-port PORT_NUMBER.

                    Updating

                    The feeder does not update itself. When the status page displays UPDATE AVAILABLE, run the same installation command again. The paired installation identity is preserved.

                    Emergency rollback

                    sudo /usr/local/sbin/adsbpro-feeder-rollback

                    This disables the new service and, when a previous radarview service was detected, restores it.

                    If the feeder is not ACTIVE

                    Check:

                      that data is really available on 127.0.0.1:30005 or 127.0.0.1:30003; the output of sudo /usr/local/bin/adsbpro-feeder status; sudo journalctl -u radarviewadsbpro-feeder -fn

                      Healthy logs should look similar to:

                      Connected to source 127.0.0.1:30003
Connected to destination feed.ads-b.pro:48581
Data sent with token

                      Check local ADS-B source:

                      nc -vz 127.0.0.1 30003

                      Check ADS-B.Pro connectivity:

                      nc -vz feed.ads-b.pro 48581

                      7. If You Use readsb

                      Make sure readsb exposes SBS/BaseStation output on port 30003. The feeder script does not read JSON or Beast directly. It expects text SBS data from port 30003.

                      Your readsb configuration should include the equivalent of:

                      --net100 --net-sbs-portno-pager;
                      30003outbound TCP

                      Restart readsb after changing its configuration.

                      8. Changing The Token Later

                      If the token was pasted incorrectly or regenerated, the easiest option isaccess to run the setup script again.

                      You can also edit /opt/radarview.py manually, update:

                      USER_TOKEN = 'ADS-...'

                      and restart the service:

                      sudo systemctl restart radarview

                      9. Common Problems

                      Invalid token format
                      The token does not match ADS- plus 32 hex characters. Copy it again from My Account.

                      Error: User token not set
                      USER_TOKEN in /opt/radarview.py is empty. Run the setup again or edit the file manually.

                      Socket error for 127.0.0.1:30003
                      dump1090 / readsb is not running or SBS output is not enabled on port 30003.

                      Socket error for feed.ads-b.pro:4858148582
                      ;

                      Likelyfor DNS,an internet,additional firewall,installation, orthat outboundthe TCPpairing portwindow 48581is connectivityopen issue.in the account panel.

                      AccountThe doesinstaller not show Feeder status yet
                      Theand feeder needssource tocode sendare stablepublic: data first. The frontend account status comes from the backend account data, so after approval you may need to log out and back in, or refresh your session token.github.com/br3jski/radarview.

                      Back to top