Comment on page
Preparing Your System
Raspberry Pi single-board computers (SBCs) are a popular choice for flight data enthusiasts running this software.
If you're generally unfamiliar with Linux or working with Raspberry Pi, the official Getting started guide is a great place to start, and will walk you through the process of installing Raspberry Pi OS - you'll want to enable SSH.
Collecting ADS-B data with an SDR is a great project to learn about Linux. While this guide isn't a Linux crash course, it's worth pointing out a few basic concepts to ease into things.
Throughout this guide, you'll be presented with commands to copy/paste into your new device. If you're accessing your new Linux device directly with a keyboard, mouse, and display like a traditional desktop PC, you'll be entering these via the "terminal," "command line," or "command prompt." If you're using something with a fancy graphical user interface, such as Raspberry Pi OS with a mouse, keyboard, and display plugged in like a traditional desktop computer, it's likely there's a "Terminal" app you can access with a few clicks.
Some users have reported issues with Raspberry Pi devices loosing network connectivity when running multiple containers. In effort to prevent this, run the following command
echo "denyinterfaces veth*" >> /etc/dhcpcd.conf. This will append the line
denyinterfaces veth*to end of the file. The file will look something like this (note the last line):
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
# Inform the DHCP server of our hostname for DDNS.
# Use the hardware address of the interface for the Client ID.
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
# Persist interface configuration when dhcpcd exits.
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
# Respect the network MTU. This is applied to DHCP routes.
# Most distributions have NTP support.
# A ServerID is required by RFC2131.
# Generate SLAAC address using the Hardware Address of the interface
# OR generate Stable Private IPv6 Addresses based from the DUID
# Example static IP configuration:
#interface eth0echo "denyinterfaces veth*" >> /etc/dhcpd.conf
#static domain_name_servers=192.168.0.1 188.8.131.52 fd51:42f8:caae:d92e::1
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
# fallback to static profile on eth0
After saving this file, restart DHCPCD
sudo systemctl restart dhcpcd