tar czf file.tar.gz input_directory

The same can be extracted with tar but indicating compression .

tar xzvf file.tar.gz output_directory

First we need to find out how the system views our drive and partitions .

pi@raspberrypi:/mnt/usb $ ls /dev/sd*
/dev/sda  /dev/sda1

Create a mount point for the drive .

$ sudo mkdir /mnt/usb

Now that we know our drive is /dev/sda and the partition is /dev/sda1 we can proceed to mount . By making use of umask=000 we allow read, write and execute for all .

$ sudo mount /dev/sda1 /mnt/usb -o umask=000

Once mounted you can view the newly mounted drive and start writing to it .

pi@raspberrypi:/mnt/usb $ df -h

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        15G   11G  3.7G  75% /
devtmpfs        459M     0  459M   0% /dev
tmpfs           463M  4.0K  463M   1% /dev/shm
tmpfs           463M  7.1M  456M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           463M     0  463M   0% /sys/fs/cgroup
/dev/mmcblk0p1   63M   21M   43M  34% /boot
/dev/sda1        30G   16K   30G   1% /mnt/usb

If PV is not installed on the system you can install it via your package manager .

$ sudo apt-get install pv

We will be directing all /dev/zero output to a file in the target drive we wish to zero-out . Once all free space is occupied in the target drive the operation will stop by itself .

$ sudo pv /dev/zero > /mnt/usb/delete.me

Sample output .

pi@raspberrypi:~ $ sudo pv /dev/zero > /mnt/usb/delete.me
 202MiB 0:00:06 [6.56MiB/s] [      <=>

Remove the resulting file .

$ rm delete.me

$ sudo apt-get install mp3wrap

Explanation of command to be executed:

• output.mp3 – this is the name of the resulting file create by Mp3Wrap
• 1.mp3, 2.mp3 – and so on… this is where you would list all files to be joined by Mp3Wrap

The resulting file will end with *_MP3WRAP.mp3.

 $ mp3wrap output.mp3 1.mp3 2.mp3

Mp3Wrap Version 0.5 (2003/Jan/16). See README and COPYING for more!
Written and copyrights by Matteo Trotta - 
THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK!

  50 %	--> Wrapping 1.mp3 ... OK
  100 %	--> Wrapping 2.mp3 ... OK

  Calculating CRC, please wait... OK

output_MP3WRAP.mp3 has been created successfully!
Use mp3splt to dewrap file; download at http://mp3splt.sourceforge.net!

By default Dump1090 interface will not display the distance between an aircraft and the site this can be easily corrected by editing a single file and providing the latitude and longitude where the receiver(yours) is located. The file in question can be located for Dump1090-mutability at

/etc/default/dump1090-mutability

Before we can start editing the configuration file first we need to obtain the latitude and longitude of the site as I assume you don’t know this information I suggest using Google Maps to obtain it.

Visit google.com/maps search for the address where the receiver is located. Once you find the site(address) right click on the location to display the menu and select What’s here?

Near the bottom of the window you should see the latitude and longitude of the site displayed. Copy this information exactly the way it appears.

My installation runs on a Raspberry Pi 2, log in to the system where Dump1090 runs and with enough permission look for and edit the following parameters LAT= latitude, LON=longitude this are the parameters well be adding the latitude and longitude information to.

sudo nano /etc/default/dump1090-mutability

# If set, supplies a reference location for local position decoding.
LAT="35.084005"
LON="-106.643967"

We are almost done now just reboot dump1090.

sudo service dump1090-mutability restart

Dump1090-mutability should start reporting the distance.

[admin@MikroTik] /ip service> print

Flags: X - disabled, I - invalid
 #   NAME                                PORT ADDRESS                                                                  CERTIFICATE
 0   telnet                                23
 1   ftp                                   21
 2   www                                   80
 3   ssh                                 22
 4 XI www-ssl                              443                                                                          none
 5   api                                 8728
 6   winbox                              8291
 7   api-ssl                             8729

From /ip service set the new SSH port number. Pick a number you like or you can use the following list https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers.

[admin@MikroTik] /ip service> set ssh port=2987

The change takes effectively immediately.

Disable a Service

Disabling a service is equally easy just type disable followed by the service name. It’s always a good idea to disable unused services. Below I’ve disable three different services.

[admin@MikroTik] /ip service> disable telnet

[admin@MikroTik] /ip service> disable ftp

[admin@MikroTik] /ip service> disable winbox

Issue the print command to verify the port change, note that certain services have a X in front of them indicating the service has been disabled.

[admin@MikroTik] /ip service> print

Flags: X - disabled, I - invalid
 #   NAME                  PORT ADDRESS                                                     CERTIFICATE
 0 XI telnet                  23
 1 XI ftp                     21
 2   www                     80
 3   ssh                   2484
 4 XI www-ssl                443                                                             none
 5   api                   8728
 6 XI winbox                8291
 7   api-ssl               8729                                                             none

Current set-up: Raspbian Jessie Lite on a Raspberry Pi 2 + RTL2832U.

Prepare Raspbian

sudo apt-get update

sudo apt-get upgrade

Dump1090 Mutability Install

Download the necessary .deb from GitHub.

wget https://github.com/mutability/mutability-repo/releases/download/v0.1.0/mutability-repo_0.1.0_armhf.deb

Install the downloaded .deb. Notice the version number.

sudo dpkg -i mutability-repo_0.1.0_armhf.deb

Once again update the installation.

sudo apt-get update

The GPG key provided with mutability-repo_0.1.0_armhf.deb expired which will result in an error every time you run apt-get we can fix the source for the error.

W: GPG error: http://repo.mutability.co.uk wheezy InRelease: The following signatures were invalid: KEYEXPIRED 1451307476 KEYEXPIRED 1451307476 KEYEXPIRED 1451307476

Now re-install mutability-repo this will pull the latest version with a valid signature.

sudo apt-get install mutability-repo

Install dump1090-mutability the version from the repository at the time of this writing was dump1090-mutability v1.14.

sudo apt-get install dump1090-mutability

Install the web server.

sudo apt-get install lighttpd

Enable module.

sudo lighty-enable-mod dump1090

Reload web server for changes to take effect.

sudo service lighttpd force-reload

Or you can reboot the entire installation which is why I recommend.

sudo reboot

On a web browser and enter the IP address for your Raspberry Pi followed by /dump1090.

http://your_ip_address/dump1090/

PiAware Install

For the latest version of PiAware check the FlightAware page. At the time of this writing the current version was piaware_2.1-5.

wget http://flightaware.com/adsb/piaware/files/piaware_2.1-5_armhf.deb

Install the downloaded package.

sudo dpkg -i piaware_2.1-5_armhf.deb

You will receive multiple errors regarding missing dependencies let apt-get install the missing dependencies.

sudo apt-get install -fy

Auto-update the PiAware Software.

sudo piaware-config -autoUpdate 1 -manualUpdate 1

Connect To FlightAware

Connect the PiAware install to flightAware by providing user credentials.

sudo piaware-config -user your_username -password

Restart PiAware.

sudo /etc/init.d/piaware restart

View the status of the install.

lventura@raspberrypi:~ $ sudo piaware-status

dump1090 is not running.
faup1090 is running.
piaware is running.
dump1090-mutabi is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090-mutabi is producing data on port 30005.

The new install should start feeding data back to FlightAware.

pi@raspberrypi:~ $ sudo piaware-status

dump1090 is not running.
faup1090 is not running.
piaware is running.
no program appears to be listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
got 'couldn't open socket: connection refused'
maybe dump1090 is NOT producing data on port 30005.

Troubleshooting steps included the following:

I tried adding the password again maybe I made a mistake but it didn’t fix the problem.

sudo piaware-config -user username -password

I know the my RTL is recognized by Raspbian.

lsusb

Bus 001 Device 011: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 010: ID 0bda:2832 Realtek Semiconductor Corp. RTL2832U DVB-T
Bus 001 Device 009: ID 05dc:a762 Lexar Media, Inc.
Bus 001 Device 013: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Tried to Restart PiAware.

sudo /etc/init.d/piaware restart

And looked for any helpful output.

cat /tmp/piaware.out

On a forum there was a suggestion about blacklisting a module.

sudo nano /etc/modprobe.d/rtlsdr.conf

Add the line below to .conf.

blacklist dvb_usb_rtl28xxu

After making the changes reboot abd run the piaware-status command hopefully your output will change.

pi@raspberrypi:~ $ sudo piaware-status

dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.

Links

https://opendesignengine.net/news/53
http://discussions.flightaware.com/ads-b-flight-tracking-f21/help-no-ads-b-data-program-is-serving-port-30005-t35812.html