Distributed Projects¶

The web interface is accessible via the port 7396, e.g. this could be:

• URL = http://<your.IP>:7396

The configuration is located in the file /mnt/dietpi_userdata/fahclient/config.xml.
You can change the configuration with the following steps:

1. Stop services with dietpi-services stop
2. Edit /mnt/dietpi_userdata/fahclient/config.xml
3. Save changes and restart services with dietpi-services start

Folding@Home has a logging feature which outputs into the journal logging system. The logs can be viewed via:

journalctl -u fahclient

In addition to the power slider in the web interface the user can influence the number of jobs that run on the system.
The example config given below has 3 job slots, ideal for a 6 core CPU (allowing 2 CPU cores per job slot):

<config>
  <!-- Slot Control -->
  <power v='FULL'/>

  <!-- User Information -->
  <user v='Fourdee'/>

  <!-- Folding Slots -->
  <slot id='0' type='CPU'/>
  <slot id='1' type='CPU'/>
  <slot id='2' type='CPU'/>
</config>

You can run many types of relay, each with their own technical requirements and legal implications.

Bridges are the safest relay to run from home, and are relatively easy, low-risk and low bandwidth, but they have a big impact on users, especially in censored countries. Normally, IP addresses and other information of Tor relays is published, making it easy for websites to blacklist the relay, and anything else using that IP address. Since a bridge isn’t listed publicly, it is unlikely to be blocked by websites or receive abuse complaints.

Guard/Middle relays are the first and second relays connected to, respectively. Information about them is listed, but they are unlikely to receive abuse complaints. However, they may be blocked by certain services that don’t understand how Tor works or deliberately want to censor Tor users. If you have one static IP address, consider running a bridge instead.

Exit relays are the final relay connected to, and the one that actually sends traffic to its destination. The website will see the exit relay’s IP address instead of the real IP address of the Tor user. Exit relays have the greatest legal exposure and liability of all the relays, and should not be run from home.

The simplest way to monitor the Tor relay is to use the DietPi-CloudShell scene, for this run dietpi-cloudshell from the command line and select the “Tor Relay” scene. It uses the Tor monitor nyx which can be called in standalone mode by executing nyx from command line.

You can also monitor it with the Tor relay search. Just paste either the fingerprint (found at /var/lib/tor/fingerprint) or nickname of your relay.

Keeping Tor relays updated is important to the safety of both the users and the operator. Because of this, automated upgrades are recommended and asked about when first installing. Otherwise, regularly run the following commands to keep your system packages up-to-date:

apt update
apt upgrade

Tor service logs can be viewed with the following command:

journalctl -t tor

The web interface is accessible via port 8090:

• URL = http://<your.IP>:8090
• Username = admin
• Password: <your global password> (default: dietpi)

Set password with:

/etc/yacy/bin/passwd.sh mypassword

Login details are then:

• Username = admin
• Password = mypassword

YaCy is extremely CPU intensive, coupled with constant background processing, we highly recommend using dietpi-services to reduce process priority.

Recommended setting: Nice = 19

The web interface is accessible via port 5003, and the gateway through 8087:

• WebUI = http://<your.IP>:5003/webui
• Gateway = http://<your.IP>:8087/ipfs/IPFSHash

You can use your IPFS node with the IPFS Companion browser extension to automatically download IPFS-hosted files through your node. In the settings page of the extension, change “IPFS API URL” to http://<your.IP>:5003, and “Local Gateway” to http://<your.IP>:8087.

Firefox: https://addons.mozilla.org/en-US/firefox/addon/ipfs-companion/

Chromium and derivatives: https://chromewebstore.google.com/detail/ipfs-companion/nibjojkomfdiaoajekhjakgkdhaomnch

You can view the service logs via

journalctl -u ipfs

You can update your IPFS node by running

dietpi-software reinstall 186

IPFS has a built in update command (ipfs update), but this requires the ipfs-update binary found at https://dist.ipfs.io/#ipfs-update.

The web interface is accessible via the port 1099, e.g. this could be:

• URL = http://<your.IP>:1099

The color of the plane icons is an indication of their altitude, lots more information (like call signs, routes of the planes, etc) are available as well. The system provides you with statistics, graphs, and information about the performance of your feeder, and makes it easy to explore some of the information provided by the aggregators that you are feeding.

First of all, you need to connect an SDR to your system (lots more information at the ADSB.impages - currently these pages are somewhat focused on the full feeder images, but all of the other information applies here as well), add an antenna and set up the software.
Then simply connect with a browser to your DietPi system on port 1099. On the initial setup page enter a name for your site plus its location and pick how you want to decide which aggregators to feed.

It will take a short while to get started (depending on your system and network speed as it will download a couple Docker containers), and after that you are up and running.

There are additional options for more advanced features, but even with just the information on the first page you’ll already start tracking planes around you. Click on the TAR1090 map link on the feeder home page to see the planes around you.

While this has been tested and works with 512MB of RAM, 1GB is a much more reasonable minimum. There seems to be no real benefit from having more than 2GB of RAM.
Decoding the data streams from the SDR is somewhat CPU intensive. A simple rule of thumb is that you want one more core than you have SDRs. So for a typical setup with one SDR for ADS-B signals (sent at 1090 MHz), two cores are sufficient. If you are in the US and also want to scan for UAT traffic (“Universal Access Transceiver” sent at 978 MHz) and therefore have two SDRs connected, three cores will get you better results.