Scroll down to the bottom of this page
Later addition:
Versions of python3 and gcc
sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/debian13/abcd567a.list
sudo wget -O /etc/apt/keyrings/abcd567a-key.gpg https://abcd567a.github.io/debian13/KEY2.gpg
sudo apt update
sudo apt install piaware
sudo piaware-config feeder-id xxxxxxxx
sudo systemctl restart piaware
sudo apt install dump1090-fa <<< Reboot required after installation
sudo apt install dump978-fa <<< Serialization of Dongles & Reboot required
sudo apt install piaware-web
sudo apt install fr24feed
sudo fr24feed --signup
sudo apt install pfclient
IP-of-Pi:30053
sudo apt install rbfeeder <<< (RPi aarch64 only - NOT for PC AMD64)
sudo rbfeeder --setkey xxxxxxxxxxxx (If you have a RB24 key)
sudo rbfeeder (If you do not have a RB24 key)
Install graphs1090 by @wiedehopf
sudo bash -c "$(wget -O - https://github.com/wiedehopf/graphs1090/raw/master/install.sh)"
Click on Screenshot to See Larger Size
Armbian Trixi uses utility sudo armbian-config to configure WiFi.
After configuring WiFi , I checked ping -c 3 google.com , and it showed WiFi is working OK.
Although piaware was able to connect to Flightaware Servers and feed data, the FlightRadar24 and RadarBox24 feeders failed to connect to their servers on WiFi. These were able to connet only on Wred Network. In spite of my repeated reconfiguration of WiFi, this problem persisted.
I got fedup and decided to use NetworkManager’s utility sudo nmtui to configure WiFi.
STEP-1: Installed NetworkManager
sudo apt install network-manager
STEP-2: Deleted file generated by armbian-config
sudo rm /etc/netplan/armbian.yaml
STEP-3: Opened default file
sudo nano /etc/netplan/10-dhcp-all-interfaces.yaml
In above file, in line renderer: systemd-networkd , replaced systemd-networkd by NetworkManager, so the line becane renderer: NetworkManager
STEP-4: Configured WiFi and Static IP by sudo nmtui
STEP-5: Run command sudo netplan apply and rebooted RPi
sudo reboot
STEP-6: SSH to RPi using the static IP address which was configured using NetworkManager’s utility sudo nmtui
STEP-7: Checked fr24feed and rbfeeder , found working OK now.
Piaware was working perfectly OK on Debian 13 Trixie SID till now.
I ran sudo apt update and sudo apt upgrade
about 80 packages were upgraded, includin itcl3 which was upgraded to ver 3.4.4-3
After the upgrade, piaware started giving following log:
abcd@debian-13:~$ sudo journalctl -u piaware -n 20
Mar 19 13:44:31 debian-13 piaware[11772]: Length = 57
Mar 19 13:44:31 debian-13 piaware[11772]: }
Mar 19 13:44:31 debian-13 piaware[11772]: unhandled TLS callback: message sock5613d8efe3b0 Received TLSv1.3 {Inner Content Type} { Inner Content Type = ApplicationData (23)
Mar 19 13:44:31 debian-13 piaware[11772]: }
Mar 19 13:44:31 debian-13 piaware[11772]: unhandled TLS callback: message sock5613d8efe3b0 Sent TLSv1.2 Header {Sent TLS Record
Mar 19 13:44:31 debian-13 piaware[11772]: Header:
Mar 19 13:44:31 debian-13 piaware[11772]: Version = TLS 1.2 (0x303)
Mar 19 13:44:31 debian-13 piaware[11772]: Content Type = ApplicationData (23)
Mar 19 13:44:31 debian-13 piaware[11772]: Length = 49
Mar 19 13:44:31 debian-13 piaware[11772]: }
Mar 19 13:44:31 debian-13 piaware[11772]: unhandled TLS callback: message sock5613d8efe3b0 Sent TLSv1.2 {Inner Content Type} { Inner Content Type = ApplicationData (23)
Mar 19 13:44:31 debian-13 piaware[11772]: }
Mar 19 13:44:32 debian-13 piaware[11772]: unhandled TLS callback: message sock5613d8efe3b0 Sent TLSv1.2 Header {Sent TLS Record
Mar 19 13:44:32 debian-13 piaware[11772]: Header:
Mar 19 13:44:32 debian-13 piaware[11772]: Version = TLS 1.2 (0x303)
Mar 19 13:44:32 debian-13 piaware[11772]: Content Type = ApplicationData (23)
Mar 19 13:44:32 debian-13 piaware[11772]: Length = 66
Mar 19 13:44:32 debian-13 piaware[11772]: }
Mar 19 13:44:32 debian-13 piaware[11772]: unhandled TLS callback: message sock5613d8efe3b0 Sent TLSv1.2 {Inner Content Type} { Inner Content Type = ApplicationData (23)
Mar 19 13:44:32 debian-13 piaware[11772]: }
abcd@debian-13:~$
abcd567 Same:
2025-03-19T20:10:03.642217+02:00 raspberrypi piaware[4083]: unhandled TLS callback: message sock55a04ffbf0 Received TLSv1.3 Handshake { CertificateRequest, Length=303
2025-03-19T20:10:03.642284+02:00 raspberrypi piaware[4083]: request_context (len=0):
2025-03-19T20:10:03.642346+02:00 raspberrypi piaware[4083]: extensions, length = 300
2025-03-19T20:10:03.642405+02:00 raspberrypi piaware[4083]: extension_type=signature_algorithms(13), length=38
2025-03-19T20:10:03.642465+02:00 raspberrypi piaware[4083]: ecdsa_secp256r1_sha256 (0x0403)
2025-03-19T20:10:03.642537+02:00 raspberrypi piaware[4083]: ecdsa_secp384r1_sha384 (0x0503)
2025-03-19T20:10:03.642603+02:00 raspberrypi piaware[4083]: ecdsa_secp521r1_sha512 (0x0603)
2025-03-19T20:10:03.642665+02:00 raspberrypi piaware[4083]: ed25519 (0x0807)
2025-03-19T20:10:03.642792+02:00 raspberrypi piaware[4083]: ed448 (0x0808)
2025-03-19T20:10:03.642890+02:00 raspberrypi piaware[4083]: rsa_pss_pss_sha256 (0x0809)
2025-03-19T20:10:03.642960+02:00 raspberrypi piaware[4083]: rsa_pss_pss_sha384 (0x080a)
2025-03-19T20:10:03.643028+02:00 raspberrypi piaware[4083]: rsa_pss_pss_sha512 (0x080b)
2025-03-19T20:10:03.643097+02:00 raspberrypi piaware[4083]: rsa_pss_rsae_sha256 (0x0804)
2025-03-19T20:10:03.643161+02:00 raspberrypi piaware[4083]: rsa_pss_rsae_sha384 (0x0805)
2025-03-19T20:10:03.643224+02:00 raspberrypi piaware[4083]: rsa_pss_rsae_sha512 (0x0806)
2025-03-19T20:10:03.643301+02:00 raspberrypi piaware[4083]: rsa_pkcs1_sha256 (0x0401)
2025-03-19T20:10:03.643365+02:00 raspberrypi piaware[4083]: rsa_pkcs1_sha384 (0x0501)
2025-03-19T20:10:03.643429+02:00 raspberrypi piaware[4083]: rsa_pkcs1_sha512 (0x0601)
2025-03-19T20:10:03.643492+02:00 raspberrypi piaware[4083]: ecdsa_sha224 (0x0303)
2025-03-19T20:10:03.643559+02:00 raspberrypi piaware[4083]: ecdsa_sha1 (0x0203)
2025-03-19T20:10:03.643623+02:00 raspberrypi piaware[4083]: rsa_pkcs1_sha224 (0x0301)
2025-03-19T20:10:03.643685+02:00 raspberrypi piaware[4083]: rsa_pkcs1_sha1 (0x0201)
2025-03-19T20:10:03.643748+02:00 raspberrypi piaware[4083]: extension_type=certificate_authorities(47), length=254
2025-03-19T20:10:03.643854+02:00 raspberrypi piaware[4083]: 0000 - 00 fc 00 80 30 7e 31 0b-30 09 06 03 55 04 06 ....0~1.0...U..
2025-03-19T20:10:03.643923+02:00 raspberrypi piaware[4083]: 000f - 13 02 55 53 31 0b 30 09-06 03 55 04 08 0c 02 ..US1.0...U....
2025-03-19T20:10:03.643991+02:00 raspberrypi piaware[4083]: 001e - 54 58 31 10 30 0e 06 03-55 04 07 0c 07 48 6f TX1.0...U....Ho
2025-03-19T20:10:03.644055+02:00 raspberrypi piaware[4083]: 002d - 75 73 74 6f 6e 31 18 30-16 06 03 55 04 0a 0c uston1.0...U...
2025-03-19T20:10:03.644123+02:00 raspberrypi piaware[4083]: 003c - 0f 46 6c 69 67 68 74 41-77 61 72 65 20 4c 4c .FlightAware LL
2025-03-19T20:10:03.644189+02:00 raspberrypi piaware[4083]: 004b - 43 31 13 30 11 06 03 55-04 0b 0c 0a 4f 70 65 C1.0...U....Ope
2025-03-19T20:10:03.644253+02:00 raspberrypi piaware[4083]: 005a - 72 61 74 69 6f 6e 73 31-21 30 1f 06 03 55 04 rations1!0...U.
2025-03-19T20:10:03.644331+02:00 raspberrypi piaware[4083]: 0069 - 03 0c 18 46 6c 69 67 68-74 41 77 61 72 65 20 ...FlightAware
2025-03-19T20:10:03.644395+02:00 raspberrypi piaware[4083]: 0078 - 49 6e 74 65 72 6d 65 64-69 61 74 65 00 78 30 Intermediate.x0
2025-03-19T20:10:03.644456+02:00 raspberrypi piaware[4083]: 0087 - 76 31 0b 30 09 06 03 55-04 06 13 02 55 53 31 v1.0...U....US1
2025-03-19T20:10:03.644522+02:00 raspberrypi piaware[4083]: 0096 - 0b 30 09 06 03 55 04 08-0c 02 54 58 31 10 30 .0...U....TX1.0
2025-03-19T20:10:03.644585+02:00 raspberrypi piaware[4083]: 00a5 - 0e 06 03 55 04 07 0c 07-48 6f 75 73 74 6f 6e ...U....Houston
2025-03-19T20:10:03.644645+02:00 raspberrypi piaware[4083]: 00b4 - 31 18 30 16 06 03 55 04-0a 0c 0f 46 6c 69 67 1.0...U....Flig
2025-03-19T20:10:03.644705+02:00 raspberrypi piaware[4083]: 00c3 - 68 74 41 77 61 72 65 20-4c 4c 43 31 13 30 11 htAware LLC1.0.
2025-03-19T20:10:03.644765+02:00 raspberrypi piaware[4083]: 00d2 - 06 03 55 04 0b 0c 0a 4f-70 65 72 61 74 69 6f ..U....Operatio
2025-03-19T20:10:03.644826+02:00 raspberrypi piaware[4083]: 00e1 - 6e 73 31 19 30 17 06 03-55 04 03 0c 10 46 6c ns1.0...U....Fl
2025-03-19T20:10:03.644904+02:00 raspberrypi piaware[4083]: 00f0 - 69 67 68 74 41 77 61 72-65 20 52 6f 6f 74 ightAware Root
2025-03-19T20:10:03.644970+02:00 raspberrypi piaware[4083]: }
2025-03-19T20:10:03.645032+02:00 raspberrypi piaware[4083]: unhandled TLS callback: message sock55a04ffbf0 Received TLSv1.2 Header {Received TLS Record
2025-03-19T20:10:03.645092+02:00 raspberrypi piaware[4083]: Header:
2025-03-19T20:10:03.645150+02:00 raspberrypi piaware[4083]: Version = TLS 1.2 (0x303)
2025-03-19T20:10:03.645208+02:00 raspberrypi piaware[4083]: Content Type = ApplicationData (23)
2025-03-19T20:10:03.645266+02:00 raspberrypi piaware[4083]: Length = 1507
2025-03-19T20:10:03.645327+02:00 raspberrypi piaware[4083]: }
Kernel bumped to 6.12 and a lot of packages.
tcl-tls package installed from Debian repository is cause of failure. Removed it and built+installed tcl-tls from source code “tcltls-rebuilt” from Flightaware
STEP-1
Purged the tcl-tls installed from Debian repository
sudo apt purge tcl-tls
Above command removed both tcl-tls and piaware (as piaware depends on tcl-tls).
STEP-2
Build and installed tcl-tls from source code from Flightaware (tcltls-rebuilt)
After installation of tcl-tls rebuilt, put it on hold so that it wont be replaced by version supplied from Debian repo during upgrades
(2.1) Created a blank file by following command:
sudo nano tcltls-rebuild.sh
(2.2) Copy-pasted code given below in above noted blank file, and saved.
#!/bin/bash
set -e
echo -e "\e[1;32mInstalling Build Tools \e[0;39m"
apt install -y \
git \
build-essential \
devscripts \
debhelper \
tcl8.6-dev \
autoconf \
echo -e "\e[1;32mInstalling tcl-tls dependencies \e[0;39m"
apt install -y \
libssl-dev \
tcl-dev \
chrpath
echo -e "\e[1;32mCloning tcl-tls source code \e[0;39m"
git clone --depth 1 https://github.com/flightaware/tcltls-rebuild
cd tcltls-rebuild
echo -e "\e[1;32mbuilding tcl-tls package \e[0;39m"
./prepare-build.sh bullseye
cd package-bullseye
dpkg-buildpackage -b --no-sign
echo -e "\e[1;32mInstalling tcl-tls package \e[0;39m"
cd ../
dpkg -i tcl-tls_*.deb
echo -e "\e[1;32mInstallation of tcl-tls completed \e[0;39m"
(2.3) Run the script file to built & install tc-ltls:
sudo bash tcltls-rebuild.sh
(2.4) After tcl-tls is built & installed by the script, put it on hold by following command to prevent it’s replacement during upgrades
apt-mark hold tcl-tls
STEP-3:
Installed piaware again
Manualy building tcl-tls, as described above, is no more required if you use any one of the following methods to install piaware. I have now updated both of these to automatically install tcl-tls built from Flightaware’s source code “tcltls-rebuild”
In responce to above noted issue which I created 2 days ago at cx_Freeze Github, the author @marcelotduarte has kindly provided a patch and a hook for cx_Freeze 8.0.0 to make it compatible with piaware_builder.
I have successfully built piaware ver 10.0 on Debian 13 Trixie using cx_Freeze 8.0.0 after applying the patch & hook. An updated version of cx_Freeze incorporating these changes is expected soon.
About 2 weeks before above issue was resolved, I have used a workaround to build piaware’s fa-mlat-client without cx_Freeze by modifying file debian/rules as follows:
build_mlat-client:
cd mlat-client && ./setup.py build && ./setup.py install
install_mlat-client:
install -d $(CURDIR)/debian/piaware/usr/lib/piaware/helpers
install -t $(CURDIR)/debian/piaware/usr/lib/piaware/helpers /usr/local/bin/fa-mlat-client
install -d $(CURDIR)/debian/piaware/usr/lib/python3/dist-packages
mv /usr/local/lib/python3.13/dist-packages/MlatClient-0.2.13-py3.13-linux-*.egg $(CURDIR)/debian/piaware/usr/lib/python3/dist-packages/
mv /usr/local/lib/python3.13/dist-packages/easy-install.pth $(CURDIR)/debian/piaware/usr/lib/python3/dist-packages/
rm /usr/local/bin/mlat-client
rm /usr/local/bin/fa-mlat-client
clean_mlat-client:
install_piaware:
Today (April 02, 2025) cx_Freeze ver 8.1.0 released
Tested on arm64 and x86_64 versions of Debianbt 13 trixie & Ubuntu 24 noble. Works like a charm.
Given below are 3 additions / alterations I have made to match the new release:
Modification 1 of 3:
Modified file piaware_builder/sensible-build.sh, as shown below
trixie)
fetch_archive cx_Freeze-8.1.0 \
https://github.com/marcelotduarte/cx_Freeze/archive/refs/tags/8.1.0.tar.gz \
45d82f7e541ae4fb05ed4250c03a84f969ba94a43bac0112a86c0b7793a12c3b
;;
noble)
fetch_archive cx_Freeze-7.2.0 \
https://github.com/marcelotduarte/cx_Freeze/archive/refs/tags/7.2.0.tar.gz \
b2846d0215fd6e18a1dccc398f71a67840d77c1fb2f5ae911d87867d4330bcfa
;;
Modification 2 of 3:
In following files, modified cx_Freeze version numbers to match version numbers of “Modification 1 of 3” :
piaware_builder/trixie/rules
piaware_builder/noble/rules
Modification 3 of 3:
The tcl-tls_1.8.0-2 provided by debian-13 apt repo resulted in failure of piaware.
Build tcl-tls using following source code, with which the piaware worked OK
git clone https://github.com/flightaware/tcltls-rebuild
Above created tcl-tls_1.7.22-2+fa1. To prevent debian repo provided newer version tcl-tls_1.8.0-2 to replace it during upgrades, put it on hold by following command:
sudo apt-mark hold tcl-tls
Image download Link:
https://dietpi.com/downloads/images/DietPi_RPi234-ARMv8-Trixie.img.xz
STEP-1:
Using Raspi Imager, wrote 64-bit raspberrypi os bookworm (Lite) image on a spare microSD card, slipped microSD card into RPi Model 4, and powered up.
STEP-2:
Replaced bookworm by trixie in following two files
sudo nano /etc/apt/sources.list
sudo nano /etc/apt/sources.list.d/raspi.list
STEP-3:
After above modifications, ran following commands:
sudo apt update
sudo apt full-upgrade
sudo apt autoremove
sudo apt autoclean
sudo reboot
STEP-4:
Built following packages from source code & Installed these:
STEP-5:
Installed graphs1090 using script at @wiedehopf 's Github site.
STEP-6:
Installed following other feeders:
sudo apt update
sudo apt install firmware-brcm80211 --fix-broken
sudo reboot
sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/debian13/abcd567a.list
sudo wget -O /etc/apt/keyrings/abcd567a-key.gpg https://abcd567a.github.io/debian13/KEY2.gpg
sudo apt update
sudo apt install dump1090-fa
sudo reboot
sudo apt install piaware
sudo piaware-config feeder-id xxxxxxxxxxxx
sudo systemctl restart piaware
sudo apt install piaware-web
sudo apt install dump978-fa
sudo piaware-config uat-receiver-type sdr
sudo systemctl restart piaware
sudo apt install fr24feed
sudo fr24feed --signup
sudo systemctl enable fr24feed
sudo systemctl restart fr24feed
sudo apt install rbfeeder
sudo apt install mlat-client
sudo rbfeeder --setkey xxxxxxxxxxxxxxxxxxx
sudo systemctl restart rbfeeder
sudo apt install pfclient
After pfclient package is installed, in browser, open page IP-of-Pi:30053 and complete configuration.
sudo bash -c "$(curl -L -o - https://github.com/wiedehopf/graphs1090/raw/master/install.sh)"