A portable RaspberryPi USB Ethernet Gadget that safeguards your Privacy
This repository functions as a guide and as a step-by-step tutorial that will help you to configure a RaspberryPi 4 as a USB Ethernet Gadget that routes all of your Mac's internet traffic through a VPN while blocking all sorts of ads and trackers and spoofing its own device identity.
When Apple made macOS BigSur publicly available in autumn 2020, we realized that our installation of Little Snitch (a host based firewall) partially stopped working. More specifically we noticed, that all Apple Processes were not filtered anymore. Strange. When we researched this problem online we came across a blog post by Jeffrey Paul (Your Computer Isn't Yours), a security researcher based in Berlin. We strongly recommend reading this article before you decide to setup your own Raspberry Pi Privacy Gadget!
A very short summary: modern macOS operating systems have the capability to bypass internal firewalls and VPN's, a possibility that is built into the operating system. Furthermore, each Apple Computer constantly connects to both Apple Servers and 3rd parties (i.e. Akamai) to transmit hashes of apps that are being used - whenever they are being used. Apple uses these hashes to prevent any malicious apps (and other blacklisted apps) from launching, if the online certificate check fails. Apple claims that this is only a security feature to combat malicious apps. While this might be true, it also means that Apple always knows when you are online, where you are while you are online, for how long you use specific software, i.e. Photoshop, or whenever you start the Tor Browser. Over time this practice amounts to a tremendous amount of data that paints a pretty accurate picture of your digital life and habits, physical movements and activity patterns. All this data can potentially be correlated with other big data, collected by corporations like Google, Microsoft, Facebook, etc. As Jeffrey Paul correctly points out:
Since October of 2012, Apple is a partner in the US military intelligence community’s PRISM spying program, which grants the US federal police and military unfettered access to this data without a warrant, any time they ask for it.
We think this is a very upsetting development, another dangerous move toward surveillance captilism, that violates the privacy of all Apple Users.
Admittedly there was huge critzism toward Apple, which is why some of these intrusions, i.e. the ContentFilterExclusionList that allowed native Apple Apps to bypass local Firewalls and VPN's, has since been revoked (A Wall without a Hole).
According to Apple, privacy is a fundamental human right:
Privacy is a fundamental human right. At Apple, it’s also one of our core values. Your devices are important to so many parts of your life. What you share from those experiences, and who you share it with, should be up to you. We design Apple products to protect your privacy and give you control over your information. It’s not always easy. But that’s the kind of innovation we believe in.
Yet we think claiming to deeply care about user privacy, while being part of programs like PRISM, shows a double-standard that should not be tolerated.
Who guarantees that something like a ContentFilterExclusionList won't suddenly re-surface with the next update? We think Apple cannot be trusted with our user data, which is the reason why we set up a Raspberry Pi Ethernet Gadget as a portable external network filtering device to make data-harvesting as difficult as as possible.
As Jeffrey Paul points out: Your computer is not yours. But it should be!
Jeffrey Paul:
https://sneak.berlin/20201112/your-computer-isnt-yours/#updates
Apple:
https://www.apple.com/privacy/
https://www.apple.com/legal/transparency/
PRISM:
https://en.wikipedia.org/wiki/PRISM_(surveillance_program)
https://www.reuters.com/article/us-apple-fbi-icloud-exclusive/exclusive-apple-dropped-plan-for-encrypting-backups-after-fbi-complained-sources-idUSKBN1ZK1CT
Objective Development:
https://blog.obdev.at/a-wall-without-a-hole/
https://blog.obdev.at/a-hole-in-the-wall/
Portable RaspberryPi USB Ethernet Gadget that safeguards your Privacy
This Raspberry Pi Privacy Gadget functions like a portable router that allows you to monitor and controll all network traffic, including native Apple processes. If you follow our guide, your Mac will be connected via USB-C to the Raspberry Pi, while the Raspberry Pi connects to the internet.
FEATURES:
- VPN: Setup your etherent gadget to route all traffic, without exception, through a VPN. We use ProtonVPN as an example. ProtonVPN features a built-in killswitch to prevent leaks. It has been independently audited and is protected by strong Swiss privacy laws. However, feel free to use any VPN provider you trust, i.e. install a Wireguard VPN on a Virtual Private Server and become your own VPN provider - or configure your Ethernet Gadget to route all traffic through Tor. It is your choice.
- Enhanced Tracking Protection: We use an existing project, the Pi-hole, as a DNS filter that blocks all requests to Apple servers, Akami, iCloud, etc. It is easy to disable, re-enable, fine-tune and configure these filters via a Web-Interface. I.e. we want to allow software updates. An additional benefit is the original purpose of the Pi-hole: It was designed as an ad blocker. As such it allows you to install blocklists that block known ads and trackers. Further you can create your own custom blocklists and allowlists.
- Encrypted DNS: We implement encrypted DOT (DNS-over-TLS) via Stubby and CZ.NIC. Stubby encrypts DNS queries sent from the Raspberry Pi to increase user privacy.
- Hidden Wifi Hotspot: In our configuration we use an additional external Wifi Antenna. This frees our built-in Wifi card to be configured as a hidden hotspot that can be used to share the same internet connection, including the VPN on the Raspberry Pi, with your other devices (i.e. your smartphone). The hotspot is configured via dnsmasq (which is already included in a Pi-hole installation) and hostapd.
- Firewall: IP-tables.
- Randomized Device Identity: Any public Wifi you connect to, from now on will only log the MAC Address and the hostname of your Ethernet Gadget, instead of your Mac's MAC Address. We randomize its MAC-Address during each reboot to further enhance your privacy. During each reboot our USB Ethernet Gadget also picks a random hostname from a dictionary.
This proposed setup only works reliable if all internet connectios are routed through the Raspberry Pi USB Ethernet Gadget, which is why we include additional instructions for a simple launch daemon that will switch off your Mac's wifi as soon as possible during the boot process (by default your Mac is configured in such a way that it starts Wifi every time you boot your machine).
- 01 - Prerequisites
- 02 - Initial Setup
- 03 - Configure external Wifi Adapter
- 04 - VPN
- 05 - Setup USB-Ethernet Gadget
- 06 - Install Pi-Hole
- 07 - Encrypted DNS
- 08 - Setup Blocklists
- 09 - Hidden Wifi Access Point
- 10 - Firewall
- 11 - Randomized Device Identity
- 12 - Optional Custom Login Information
- 13 - Disable Wifi on MacOS
- 14 - To Do
We use a Raspberry Pi 4B (8Gb). The USB-C cable needs to be of good quality and support fast data transfers. We use the USB-C cable of an external SSD drive (G-DRIVE). Further we use this tiny Wifi-Adapter: Alfa AWUS036ACS. It is fast and reliable. If you choose to use this adapter you will have to compile the required kernel module. We included the necessary steps in this guide. However, there are other wifi adapters that work natively on the Raspberry Pi. Further you will need a fast SD Card (i.e. 32GB by SanDisk).
A case for the Raspberry Pi and a cooling system. We can recommend the Pibow Case and the lightweight Fanshim by Pimoroni.
You will need a clean install of Raspberry Pi OS - Lite without desktop environment. Instructions how to install it on a micro SD-Card can be found on this site. To complete this guide with a Raspberry Pi 4, we recommend you download the latest 64bit system here.
After flushing the operating system onto your SD-Card, open the Terminal.app on your Mac and execute the following command to enable ssh access:
touch /Volumes/boot/ssh
Then enable internet connectivity by creating this file:
nano /Volumes/boot/wpa_supplicant.conf
Insert:
ctrl_interface=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=de
network={
ssid="your-network"
scan_ssid=1
psk="your-wifi-password"
key_mgmt=WPA-PSK
priority=1
}
IMPORTANT: Change the value your-network to the network you want to connect to, and your-wifi-password to the required Wifi password and adjust the country code (in this example de) to your location!
Also before you insert the SD-card into your Raspberry Pi, you need to create a user and a password. The former standard user pi has been deprecated by the Rasperry Pi Foundation. Because we are doing a headless setup without desktop environment your user has to be created before the first boot. Execute these four commands to create your new user (replace username and password with a username and a password of your choice):
echo 'username:' > /Volumes/boot/tmp.txt
echo 'password' | openssl passwd -6 -stdin >> /Volumes/boot/tmp.txt
tr -d '\n' < /Volumes/boot/tmp.txt > /Volumes/boot/userconf.txt
rm /Volumes/boot/tmp.txt
Next insert the SD-Card into your Raspberry Pi and boot it up.
There are several ways to find your Raspberry Pi on your local network. You could log into your router and look up its address.
One way to find the Raspberry Pi on your network is this command:
arp -a
Once you find the local IP address of your Pi, open a terminal window and connect via ssh, i.e.:
ssh username@192.168.8.168 (Username and password are the username and password you set up in the previous step).
You might want to update your timezone and locales by executing the following commands:
export LANGUAGE="en_GB.UTF-8"
export LANG="en_GB.UTF-8"
export LC_ALL="en_GB.UTF-8"
Also select your desired locales with this command:
sudo dpkg-reconfigure locales
Then edit /etc/default/locale:
sudo nano /etc/default/locale
For British English, insert:
LANG=en_GB.UTF-8
LC_ALL=en_GB.UTF-8
LANGUAGE=en_GB.UTF-8
To set your timezone, i.e.:
sudo timedatectl set-timezone Europe/Berlin
Before you proceed, update your Raspberry Pi:
sudo apt update && sudo apt upgrade -y
To make sure your user will be logged in on boot, run:
sudo raspi-config
Navigate to 1 System Options and select Boot / Auto login. Select Console Autologin. Please note that raspi-config is constantly being developed. The location of the required menu item might change! Then, reboot your Raspberry Pi.
SSH:
We strongly recommend you tighten your SSHD login security. Change the default SSH port from 22 to an unused port of your choice.
sudo nano /etc/ssh/sshd_config
Find and change this line:
#port 22
Also we suggest you enable key-based authentication instead of password based authetication. This tutorial should get you started: https://pimylifeup.com/raspberry-pi-ssh-keys/
Even better: get a hardwarekey (Nitrokey or Yubikey)
Another option is two-factor authentication: https://pimylifeup.com/setup-2fa-ssh/
SUDO:
We recommend you ask for a password when you use sudo:
sudo nano /etc/sudoers.d/010_pi-nopasswd
Replace its content with (username is the username you set up earlier):
username ALL=(ALL) PASSWD: ALL
If you use an external wifi adapter that works out of the box, you can skip this step.
Our external Wifi Adapter is the Alfa AWUS036ACS. This wifi adapter is small and unobtrusive. But we want to use this wifi adapter mainly for one reason: a good wifi adapter that supports USB3 connected to one of the Raspberry Pi's USB3 ports is faster and performs better than the built in wifi card. Unfortunately this wifi antenna does not work out of the box. We need to compile its drivers. If you want to use another wifi adapter than the Alfa AWUS036ACS, that does not work out of the box you will have to research online how to compile the required driver.
Install dependencies:
sudo apt install git raspberrypi-kernel-headers dkms -y
Then clone the required git repository:
mkdir Compile
cd Compile
git clone -b v5.6.4.2 https://github.com/aircrack-ng/rtl8812au.git
cd rtl*
You will need to run those commands below which builds the ARM64 arch driver. If you run a 32-bit version of Raspian OS, you can find detailed instructions here.
sed -i 's/CONFIG_PLATFORM_I386_PC = y/CONFIG_PLATFORM_I386_PC = n/g' Makefile
sed -i 's/CONFIG_PLATFORM_ARM64_RPI = n/CONFIG_PLATFORM_ARM64_RPI = y/g' Makefile
export ARCH=arm
sed -i 's/^MAKE="/MAKE="ARCH=arm\ /' dkms.conf
sudo make && sudo make install
If you ever need to uninstall this driver:
cd Compile/rtl*
sudo make dkms_remove
After every update of the raspberrypi-kernel-headers you will have to recompile this driver, because each update of the raspberrypi-kernel-headers will delete it!
DRIVER OPTIONS:
Driver options for example let you turn off the blinking LED of the Wifi-Adapter. More importantly they enable you to switch the adapter to use USB3 instead of USB2. The following file contains possible options and instructions of how to use them. Read it!
Create /etc/modprobe.d/88XXau.conf:
sudo nano /etc/modprobe.d/88XXau.conf
Insert:
# /etc/modprobe.d/88XXau.conf
#
# Purpose: Allow easy access to specific driver options.
# To see all options that are available:
#
# -----
#
# $ ls /sys/module/88XXau/parameters/
#
# Edit the following line to change options:
options 88XXau rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgnt=1 rtw_switch_usb_mode=1
#
# After editing is complete, save this file and reboot to activate the changes.
#
# Documentation:
#
# -----
#
# Log level options: ( rtw_drv_log_level )
#
# 0 = NONE (default)
# 1 = ALWAYS
# 2 = ERROR
# 3 = WARNING
# 4 = INFO
# 5 = DEBUG
# 6 = MAX
#
# Note: You can save a log file that only includes RTW log entries by running the following in a terminal:
#
# $ sudo ./save-log.sh
#
# -----
#
# LED control options: ( rtw_led_ctrl )
#
# 0 = Always off
# 1 = Normal blink (default)
# 2 = Always on
#
# -----
#
# VHT enable options: ( rtw_vht_enable )
#
# 0 = Disable
# 1 = Enable (default)
# 2 = Force auto enable (use caution)
#
# Notes:
# - Unless you know what you are doing, don't change the default for rtw_vht_enable.
# - A non-default setting can degrade performance greatly in some operational modes.
# - For 5 GHz band AP mode, setting this option to 2 will allow 80 MHz channel width.
#
# -----
#
# Power saving options: ( rtw_power_mgnt )
#
# 0 = Disable power saving
# 1 = Power saving on, minPS (default)
# 2 = Power saving on, maxPS
#
# Note: Extensive testing has shown that the default setting works well.
#
# -----
#
# USB mode options: ( rtw_switch_usb_mode )
#
# 0 = No switch
# 1 = Switch from usb 2.0 to usb 3.0
# 2 = Switch from usb 3.0 to usb 2.0 (default)
We noticed, that sometimes the external wifi adapter is called wlan0, sometimes wlan1. However we want to assign a persistent reliable names across reboots. To achieve this we decided we always plug our wifi adapter into the upper USB3 port. We need to change udev rules to ensure it is always called wlan1 and the built-in wifi is always called wlan0:
sudo ln -nfs /dev/null /etc/systemd/network/99-default.link
Next create a new rule /etc/udev/rules.d/70-persistent-net.rules:
sudo nano /etc/udev/rules.d/70-persistent-net.rules
Insert:
# Layout Raspberry Pi 4B:
#
# +-------+-------+-----+
# | | wlan1 | |
# +-------+-------+ RJ45|
# | wlan3 | wlan2 | |
# +-------+-------+-----+
# | wlan0 | ............. => (onboard wifi)
#
# Based on output: udevadm info -a /sys/class/net/wlan1
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="sdio", KERNELS=="mmc1:0001:1", NAME="wlan0"
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", KERNELS=="1-1.1", NAME="wlan1"
#ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", KERNELS=="1-1.2", NAME="wlan2"
#ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", KERNELS=="1-1.4", NAME="wlan3"
This ensures that the onboard wifi will always be called wlan0 and any wifi adapter plugged into the upper USB3 port will be called wlan1.
Now insert your wifi adapter into the upper USB3 port and reboot your Raspberry Pi.
Reboot:
sudo reboot now
https://github.com/aircrack-ng/rtl8812au
Next we configure our Raspberry Pi to route all traffic, without exception, through a VPN. We use ProtonVPN as an example. ProtonVPN has been independently audited and is protected by strong Swiss privacy laws. If you want to use ProtonVPN as well, you first have to visit their website and open account. You can use a free account or choose one of the paid options. There is a commandline tool by ProtonVPN, however it does not work on a Raspberry Pi, which is why we use the community build.
To install ProtonVPN, execute the following two commands:
sudo apt install openvpn dialog python3-pip python3-setuptools -y
sudo pip3 install protonvpn-cli
Further we need to install iptables, which we will later also use to setup our Firewall:
sudo DEBIAN_FRONTEND=noninteractive apt install -y netfilter-persistent iptables-persistent
To forward all traffic through the VPN we also need to setup the required iptable rule:
sudo iptables -t nat -A POSTROUTING -o proton0 -j MASQUERADE
sudo netfilter-persistent save
You need to initialize ProtonVPN only once. In future your RaspberryPi will connect automatically:
sudo protonvpn init
You will be asked to enter your ProtonVPN username, your password and to choose your ProtonVPN subscription plan (enter whatever plan you purchased, i.e. Free, Basic or Plus) to complete the initialization.
To configure ProtonVPN run the following command:
sudo protonvpn configure
Here you can change all of your settings, i.e. change the DNS Management of your VPN service or change the default protocol (we recommend TCP), etc. Please consider that the Kill Switch may later interfere with your Pi-hole in a negative way. If you suddenly cannot connect anymore, we recommend you disable the Kill Switch and try again. The Pi-hole will most likely bypass your VPN's DNS-settings if you disable the Kill Switch (we did not test this).
To check the connection status of ProtonVPN, execute:
protonvpn status
sudo nano /etc/systemd/system/protonvpn.service
Insert:
[Unit]
Description=Proton VPN
After=syslog.target network-online.target
Wants=network-online.target
[Service]
Type=forking
ExecStart=/usr/local/bin/protonvpn c --sc
ExecStop=/usr/local/bin/protonvpn d
ExecReload=/usr/local/bin/protonvpn c --sc
Environment=SUDO_USER=username
Restart=always
RestartSec=2
[Install]
WantedBy=multi-user.target
Please don't forget to adjust the username in the Line Environment=SUDO_USER=username to your username!
Unless you subscribed for a Plus Membership the above system service won't work, as it attempts to use ProtonVPN's secure core which is only available to paying Plus Members. If you always want to connect to the fastest server (any membership), insert these lines instead:
[Unit]
Description=Proton VPN
After=syslog.target network-online.target
Wants=network-online.target
[Service]
Type=forking
ExecStart=/usr/local/bin/protonvpn c --fastest
ExecStop=/usr/local/bin/protonvpn d
ExecReload=/usr/local/bin/protonvpn c --fastest
Environment=SUDO_USER=username
Restart=always
RestartSec=2
[Install]
WantedBy=multi-user.target
Again - Please don't forget to adjust the username in the Line Environment=SUDO_USER=username to your username!
You change the protonvpn command in this System Service according to your own preferences. I.e. if you always want to connect to a random server, replace --fastest with --random. To see all available options, run:
protonvpn -h
Enable and start protonvpn.service:
sudo systemctl enable protonvpn.service
sudo systemctl start protonvpn.service
If all DNS requests were handled by ProtonVPN (i.e. if you keep DNS-leak Protection and Kill Switch enabled), your Pi-hole might missbehave. This is the reason why we recommend to disable the Kill Switch in this specific setup. Also we recommend you disable DNS Managment in the ProtonVPN settings because we want our Pi-hole to manage all DNS requests to filter ads, trackers and malware - even while we use our VPN Service. We will configure our Pi-hole to listen on ALL INTERFACES.
This step also is very important. The Raspberry Pi has no on-board realtime clock and needs an internet connection to synchronise time. However, if you set up a VPN we noticed that our Pi tries to sync time through the VPN after it booted. But because the time is off (we had ist switched off over night) the VPN refused to connect, which means we were not able to connect to the interent anymore. Further, aou may want to connect to a privacy respecting time server, i.e. from dismail.de. To use custom timeservers edit this file:
sudo nano /etc/systemd/timesyncd.conf
Below [Time], insert (example: timeservers by dismail.de):
NTP=ntp1.dismail.de ntp2.dismail.de ntp3.dismail.de
Further we need to enable split tunneling in our VPN configuration and exclude the IP's of our timeserver from using the VPN:
sudo protonvpn configure
Select 6) Split Tunneling and enter the following IP's:
213.136.94.10
80.241.218.68
78.46.223.134
If you want to use IPv6 as well, enter the following IP6 too:
2a02:c207:3000:6091::1
2a02:c205:3001:4558::1
2a01:4f8:c17:e5e::2
Reboot your device to make your changes take effect.
Other configuration options we do recommend:
sudo protonvpn configure
Select 4) DNS Management and then 3) Disable DNS Management
Further:
sudo protonvpn configure
Select 5) Kill Switch and then 3) Disable Kill Switch
IPv6 may be a privacy risk (we neither confirm nor oppose this claim). If you are unsure, you may disable IPv6 altogether to prevent DNS leaks:
sudo nano /etc/sysctl.conf
Insert at the end:
# Disable IPv6
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
To make your changes take effect, run this command or reboot your device:
sudo sysctl -p
Now we will configure the Raspberry Pi as a USB-Ethernet device that connects to your Mac via USB-C. We need to configure the Pi to load additional modules so that usb0 (the direct connection to our Mac via USB-C) becomes available as a network interface. Further we assign a static IP-address to this interface. For the usb0 interface to become available with each reboot we also need to create a script and a system service that executes this script every time the Raspberry Pi boots up.
Make sure rpi-eeprom is installed:
sudo apt install rpi-eeprom -y
First edit /boot/config.txt:
sudo nano /boot/config.txt
Insert this line at the end of the file:
dtoverlay=dwc2
Next edit /boot/cmdline.txt:
sudo nano /boot/cmdline.txt
Insert:
modules-load=dwc2
IMPORTANT:
Do not start a new line. Insert at the end of the long line after rootwait. The only separation should be a single space.
Then edit /etc/modules:
sudo nano /etc/modules
Insert at the bottom in a new line:
libcomposite
Now we have defined the required modules. Next we assign a static IP-address to usb0 by editing /etc/dhcpcd.conf:
sudo nano /etc/dhcpcd.conf
Insert at the end of the file:
interface usb0
static ip_address=192.168.77.1/24
Now we need to enable routing and masquerading to forward internet traffic from wlan1 to other interfaces.
sudo nano /etc/sysctl.d/routed-ap.conf
Insert:
# Enable IPv4 routing
net.ipv4.ip_forward=1
Also find and uncomment this line in /etc/sysctl.conf:
sudo nano /etc/sysctl.conf
Edit:
net.ipv4.ip_forward=1
We already enabled forwarding to our VPN interface. As a fallback, enable forwarding from wlan1 and eth0 with the required iptable rule:
sudo iptables -t nat -A POSTROUTING -o wlan1 -j MASQUERADE
sudo netfilter-persistent save
The Raspberry Pi is supposed to function similiar to a portable router. To achieve this we will use dnsmasq as a DNS forwarder and DHCP server. However, we have to keep in mind that we also want to use the Pi-hole (see next step) as an ad blocker and network filter. The Pi-hole comes bundled with its own version of dnsmasq, which will be in conflict with any other existing installation of dnsmasq. Thus, for now we will only set up our configuration files without installing dnsmasq. This also means, that the USB-Ethernet Gadget will not yet be able to connect to your Mac to the internet. It will only be able to connect to the internet after you install Pi-hole. Then it will forward all traffic between usb0 and proton0 according to the iptable rule we set up for our VPN.
Create configuration folder and main configuration file:
sudo mkdir /etc/dnsmasq.d
sudo nano /etc/dnsmasq.conf
Insert:
conf-dir=/etc/dnsmasq.d
Next create the configuration file for usb0:
sudo nano /etc/dnsmasq.d/00-dnsmasq.conf
Insert:
# USB Gadget
interface=usb0 # USB interface
dhcp-range=set:usb0,192.168.77.2,192.168.77.254,255.255.255.0,24h
dhcp-option=set:usb0,3,192.168.77.1
# Default Gateway
address=/access.tardigrade/192.168.77.1
# Alias for this router
Finally we also need to create a script that enables our usb0 interface:
sudo nano /root/usb.sh
Insert:
#!/bin/bash
cd /sys/kernel/config/usb_gadget/
mkdir -p pi4
cd pi4
echo 0x1d6b > idVendor # Linux Foundation
echo 0x0104 > idProduct # Multifunction Composite Gadget
echo 0x0100 > bcdDevice # v1.0.0
echo 0x0200 > bcdUSB # USB2
echo 0xEF > bDeviceClass
echo 0x02 > bDeviceSubClass
echo 0x01 > bDeviceProtocol
mkdir -p strings/0x409
echo "fedcba9877543777" > strings/0x409/serialnumber
echo "Term7" > strings/0x409/manufacturer
echo "Tardigrade" > strings/0x409/product
mkdir -p configs/c.1/strings/0x409
echo "Config 1: ECM network" > configs/c.1/strings/0x409/configuration
echo 250 > configs/c.1/MaxPower
# Add functions here
# see gadget configurations below
# End functions
mkdir -p functions/ecm.usb0
HOST="00:dc:c8:f7:75:14" # "HostPC"
SELF="00:dd:dc:eb:6d:a1" # "BadUSB"
echo $HOST > functions/ecm.usb0/host_addr
echo $SELF > functions/ecm.usb0/dev_addr
ln -s functions/ecm.usb0 configs/c.1/
udevadm settle -t 5 || :
ls /sys/class/udc > UDC
# Start USB Gadget
ifconfig usb0 up
Make /root/usb.sh executable:
sudo chmod +X /root/usb.sh
Before we create a System Service that brings up the USB interface at boot time, perform a reboot and bring up your USB interface manually:
sudo reboot now
sudo ifconfig usb0 up
We do this before we install and configure our Pi-Hole, so that we get the option during its setup process to use usb0 as our listening interface.
Now create System Service to bring up USB interface on boot:
sudo nano /lib/systemd/system/usb.service
Insert:
[Unit]
Description=USB Gadget
After=network.target
[Service]
ExecStart=/bin/bash /root/usb.sh
[Install]
WantedBy=multi-user.target
Enable service and unblock wlan:
sudo systemctl enable usb.service
sudo rfkill unblock wlan
It is important, that you install the Pi-Hole now and do not reboot your Pi before the Pi-Hole is installed!
For this part of this guide we used these two resources:
Official Raspberry Pi documentation: https://www.raspberrypi.org/documentation/configuration/wireless/access-point-routed.md
Tutorial by Ben Hardill: https://www.hardill.me.uk/wordpress/2019/11/02/pi4-usb-c-gadget/
We would like to thank the Raspberry Pi Foundation and Ben Hardill for the great tutorials that made this privacy gadget possible!
Pi-hole is a Linux network-level advertisement and Internet tracker blocking application which acts as a DNS sinkhole and in our configuration also as a DHCP server, intended for use on a private network. It is designed for low-power embedded devices with network capability, such as the Raspberry Pi.
Pi-hole
cd Compile
git clone --depth 1 https://github.com/pi-hole/pi-hole.git Pi-hole
cd "Pi-hole/automated install/"
sudo bash basic-install.sh
During the installation process you will be asked to enter your preferred DNS Provider, IPv4 address, default gateway, DHCP-Range, etc. Please enter the following information when prompted:
Select YES
Ok
Ok
OK
OK
Ok
Ok
OK
OK
OK
OK
After a short installation period you will see this window:
OK
To enable your Pi-hole as your dhcp server, execute the following command:
sudo pihole -a enabledhcp "192.168.77.1" "192.168.77.255" "192.168.77.1" "24" "username"
If you want to change the password of your Pi-hole, execute this comand:
pihole -a -p
To update the Pi-hole, execute this command:
pihole -up
To update all blocklists, execute this command:
pihole -g
Now it is time to reboot your Raspberry Pi:
sudo reboot now
On your Mac, open System Preferences -> Network Settings
After a short while your Raspberry Pi should show up as Tardigrade. If it appears with a green dot (Connected), you should be able to browse the internet with all your traffic being sent through ProtonVPN, even if your Mac's WI-FI is switched off. To check if your traffic is routed through your VPN, browse to https://dnsleaktest.com and compare the IP-address that is shown with the output of this command:
protonvpn status
All your traffic should now be routed through your VPN.
You should now be able to log into your Privacy Gadget directly via SSH with either of these commands:
ssh username@192.168.77.1
ssh username@access.tardigrade
A very big THANK YOU to the developers of the Pi-hole. This is a great project! https://pi-hole.net/
Right now use unbound as a recursive resolver for encrypted DNS requests and to validate DNSSEC. Finally we will configure our Pi-hole to use unbound for all DNS requests and to use DNSSEC.
Install unbound:
sudo apt install unbound -y
Create the configuration file for unbound:
/etc/unbound/unbound.conf.d/pi-hole.conf
Insert:
server:
# If no logfile is specified, syslog is used
# logfile: "/var/log/unbound/unbound.log"
verbosity: 0
interface: 127.0.0.1
port: 5335
do-ip4: yes
do-udp: yes
do-tcp: yes
# May be set to yes if you have IPv6 connectivity
do-ip6: no
# You want to leave this to no unless you have *native* IPv6. With 6to4 and
# Terredo tunnels your web browser should favor IPv4 for the same reasons
prefer-ip6: no
# Use this only when you downloaded the list of primary root servers!
# If you use the default dns-root-data package, unbound will find it automatically
root-hints: "/var/lib/unbound/root.hints"
# Trust glue only if it is within the server's authority
harden-glue: yes
# Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
harden-dnssec-stripped: yes
# Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
# see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
use-caps-for-id: no
# Reduce EDNS reassembly buffer size.
# IP fragmentation is unreliable on the Internet today, and can cause
# transmission failures when large DNS messages are sent via UDP. Even
# when fragmentation does work, it may not be secure; it is theoretically
# possible to spoof parts of a fragmented DNS message, without easy
# detection at the receiving end. Recently, there was an excellent study
# >>> Defragmenting DNS - Determining the optimal maximum UDP response size for DNS <<<
# by Axel Koolhaas, and Tjeerd Slokker (https://indico.dns-oarc.net/event/36/contributions/776/)
# in collaboration with NLnet Labs explored DNS using real world data from the
# the RIPE Atlas probes and the researchers suggested different values for
# IPv4 and IPv6 and in different scenarios. They advise that servers should
# be configured to limit DNS messages sent over UDP to a size that will not
# trigger fragmentation on typical network links. DNS servers can switch
# from UDP to TCP when a DNS response is too big to fit in this limited
# buffer size. This value has also been suggested in DNS Flag Day 2020.
edns-buffer-size: 1232
# Perform prefetching of close to expired message cache entries
# This only applies to domains that have been frequently queried
prefetch: yes
# One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine, it should be unnecessary to seek performance enhancement by increasing num-threads above 1.
num-threads: 1
# Ensure kernel buffer is large enough to not lose messages in traffic spikes
so-rcvbuf: 1m
# Ensure privacy of local IP ranges
private-address: 192.168.0.0/16
private-address: 169.254.0.0/16
private-address: 172.16.0.0/12
private-address: 10.0.0.0/8
private-address: fd00::/8
private-address: fe80::/10
We also want to download the the current root hints file:
wget https://www.internic.net/domain/named.root -qO- | sudo tee /var/lib/unbound/root.hints
Do avoid dnsmasq warnings ain your Pi-Hole about reducing DNS packet size for nameserver 127.0.0.1 to 1232 add this configuration file:
sudo nano /etc/dnsmasq.d/99-edns.conf
Insert:
edns-packet-max=1232
Finally, make sure that unbound is used globally on all outward facing network interfaces:
sudo nano /etc/dhcpcd.conf
Insert at the end:
interface wlan1
static domain_name_servers=127.0.0.1
interface eth0
static domain_name_servers=127.0.0.1
Next we want to disable resolvconf for unbound because it is interfering with the static domain name server setting in /etc/dhcpcd.conf:
sudo systemctl disable unbound-resolvconf.service
sudo systemctl stop unbound-resolvconf.service
Futher you can tell ProtonVPN to use unbound for DNS resloution:
sudo protonvpn configure
Select 4) DNS Management, then 2) Configure Custom DNS Servers and enter:
127.0.0.1
Reboot:
sudo reboot now
Check which nameserver is used:
cat /etc/resolv.conf
If you see only this nameserver, your configuration is correct:
nameserver 127.0.0.1
Run the dig command to test DNS resolution. You should see the status as “NOERROR” with an IP address for the pi-hole.net server:
dig pi-hole.net @127.0.0.1 -p 5335
The final test is to ensure that DNSSEC is working properly. If the following commands are returned properly, DNSSEC is properly working.
This command should return SERVFAIL with NO IP address:
dig sigfail.verteiltesysteme.net @127.0.0.1 -p 5335
This command should return NOERROR WITH an IP address:
dig sigok.verteiltesysteme.net @127.0.0.1 -p 5335
To configure Pi-hole to use stubby, we log into the pi-hole web interface. Here you can also install additional blocklists, setup your own custom blocklists, view query logs, etc.
To log into your Pi-hole, open your Mac's web browser and enter this address into the address bar:
http://192.168.77.1/admin/index.php?login
To log in, enter the password that was generated at the final step of the Pi-hole installation process, unless you already changed your password earlier.
Then, navigate to Settings. Since you are already in Settings, you can change in API / Web Interface the appearance of the web interface if you like, i.e. to Star Trek LCARS theme (dark):
Click on Setting and select DNS. Make sure all boxes for pre-configured DNS providers are unchecked!
Further, delete all Upstream DNS Servers. Then enter the local address of your unbound installation as your only Custom DNS Server and tick the box that says Use DNSSEC:
127.0.0.1#5335
Your Pi-Hole might notify you after each reboot that interface usb0 does not currently exist. This happens because Pi-Hole gets started before the interface becomes available. There is nothing to worry about. However, if it annoys you, try to add a delay before Pi-Hole starts:
sudo nano /etc/pihole/pihole-FTL.conf
Insert:
DELAY_STARTUP=7
Unbound:
https://nlnetlabs.nl/projects/unbound/about/
Pihole-Unbound: https://docs.pi-hole.net/guides/dns/unbound/
DNSSEC: https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en
Still in your Pi-hole web interface, navigate to Group Management / Adlists. Here you can add new blocklists. We strongly recommend Steven Black's blocklist for fakenews, gambling, social trackers:
https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling-social/hosts
Further we can recommend the following blocklists:
- https://phishing.army/download/phishing_army_blocklist_extended.txt
- https://blocklistproject.github.io/Lists/alt-version/malware-nl.txt
- https://blocklistproject.github.io/Lists/alt-version/ransomware-nl.txt
- https://blocklistproject.github.io/Lists/alt-version/phishing-nl.txt
- https://curben.gitlab.io/malware-filter/urlhaus-filter-domains.txt
- https://raw.githubusercontent.com/ShadowWhisperer/BlockLists/master/Lists/Malware
- https://v.firebog.net/hosts/Prigent-Phishing.txt
- https://www.github.developerdan.com/hosts/lists/amp-hosts-extended.txt
Under Blacklist Management you can set your own custom blocklists. In this example we block ALL CONNECTIONS to apple servers and related 3rd parties. We use RegEx filters for:
apple, icloud, apple-cloudkit, mzstatic, aaplimg, oscp
If you block apple, icloud, apple-cloudkit, mzstatic, aaplimg, oscp via RegEx, your Mac won't be able to check for Updates, download Updates, connect to iCloud or to the App-Store. FaceTime, Messages and other native macOS Apps won't be able to connect. This may be exactly what you want, but probably not. It requires a lot of patience, work and effort to fine-tune your custom filters. I.e. check your Query Log reqularly when you try to check for updates, to see which connections are blocked. Then try to whitelist specific processes which are required to perform an update.
Alternatively you could also log into your Ph-hole web interface and temporarily disable all RegEx Filters, then check for updates and re-enable your custom blocklists once you are done.
To update all blocklists, execute this command:
pihole -g
09 - Hidden Wifi Access Point
Sometimes, i.e. when you wiggle the USB-C cable, your connection to the RaspberryPi Privacy Gadget may become interrupted. If there was also a Hidden Wifi Access Point, you would still be able to connect to your Privacy Gadget, even if the USB-C connection was interrupted. Another benefit of a Hidden Wifi Access Point is, that you could share the internet conenction of the Privacy Gadget, i.e. with your Smartphone as well. Simply log in and all traffic on your Smartphone will be filtered and routed through your VPN. Also you could connect your Privacy Gadget to a power bank in your backback, connect to its Hidden Wifi Access Point and enjoy all its benefits. In out setup we use the RaspberryPi's built-in Wifi Card as Access Point.
Install the required software:
sudo apt install hostapd -y
Then execute these commands:
sudo rfkill unblock wlan
sudo systemctl unmask hostapd
Next, add the wifi interface to dhcpcd.conf:
sudo nano /etc/dhcpcd.conf
Add these lines at the end:
interface wlan0
static ip_address=192.168.79.1/24
nohook wpa_supplicant
We also need to add the interface to our Pi-hole configuration (dnsmasq):
sudo nano /etc/dnsmasq.d/00-dnsmasq.conf
Insert at the end:
# Wifi-AP
interface=wlan0 # Access Point
dhcp-range=set:wlan0,192.168.79.2,192.168.79.22,255.255.255.0,24h
# Pool of IP addresses served via DHCP
dhcp-option=wlan0,3,192.168.79.1
# Default Gateway
Finally we configure our Hidden Wifi Access Point:
sudo nano /etc/hostapd/hostapd.conf
Insert:
interface=wlan0
hw_mode=g
channel=7
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=2
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
country_code=DE
ssid=HiddenAP
wpa_passphrase=Passphrase_for_my_hidden_AP!
Change the country code to your location and pick an ssid and wpa_passphrase of your choice!
In this setup your Wifi hotspot will be hidden. This means it will not automatically show up in your list of available networks. Instead you need to select other in your Mac's Network list and type both, Network Name and Password in order to connect.
If you want your Hidden Wifi Access Point to be a Visible Wifi Access Point, change the parameter behind ignore_broadcast_ssid to 0.
To disable your Wifi Access Point from starting automatically run this command:
sudo systemctl disable hostapd.service
To switch it on and off manually:
sudo systemctl start hostapd.service
sudo systemctl start hostapd.service
Configure your Pi-hole to listen on all interfaces:
pihole -a -i all
Official Raspberry Pi documentation:
https://www.raspberrypi.org/documentation/configuration/wireless/access-point-routed.md
It is important to secure your Raspberry Pi. For that purpose we configure a firewall via iptables. To make it easier for you we set up iptable scripts that you can run at any moment to enable your firewall rules, and also to delete them if you run into connectivity problems. We cover some firewall rules we think are important. Feel free to edit and expand on these scripts. We provide a separate script for both IPv4 and IPv6 connections.
mkdir Script
mkdir Script/iptables
sudo nano Script/iptables/iptables.sh
Insert:
#/bin/sh
# Since there only can be a wired connection between the Pi and your computer, allow all traffic on usb0:
iptables -I INPUT -i usb0 -j ACCEPT
# Accept also input on Wifi-Hotspot (we keep it hidden):
iptables -I INPUT -i wlan0 -j ACCEPT
# Allow DNS needed for name resolution (Pi-hole):
iptables -A INPUT -p tcp --destination-port 53 -j ACCEPT
iptables -A INPUT -p udp --destination-port 53 -j ACCEPT
# Allow SSH only via USB and Wifi-AP:
iptables -A INPUT -i wlan0 -p tcp --destination-port 7666 -j ACCEPT
# Allow TCP/IP to do three-way handshakes:
iptables -I INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
# Allow loopback traffic:
iptables -I INPUT -i lo -j ACCEPT
# Reject all access from anywhere else:
iptables -P INPUT DROP
# Block HTTPS advertisements to improve blocking ads that are loaded via HTTPS and also deal with QUIC:
iptables -A INPUT -p udp --dport 80 -j REJECT --reject-with icmp-port-unreachable
iptables -A INPUT -p tcp --dport 443 -j REJECT --reject-with tcp-reset
iptables -A INPUT -p udp --dport 443 -j REJECT --reject-with icmp-port-unreachable
# Block Ping Requests:
iptables -A INPUT -p icmp --icmp-type echo-request -j DROP
# Save iptables
netfilter-persistent save
For IPv6:
sudo nano Script/iptables/ip6tables.sh
Insert:
#/bin/sh
# Since there only can be one wired connection between the Pi and your computer, allow all traffic on usb0:
ip6tables -I INPUT -i usb0 -j ACCEPT
# Accept also input on Wifi-Hotspot (we keep it hidden):
ip6tables -I INPUT -i wlan0 -j ACCEPT
# Allow DNS and HTTP needed for name resolution (Pi-hole) and accessing the Web interface on Wifi-Hotspot::
ip6tables -A INPUT -p tcp --destination-port 53 -j ACCEPT
ip6tables -A INPUT -p udp --destination-port 53 -j ACCEPT
ip6tables -A INPUT -i wlan0 -p tcp --destination-port 80 -j ACCEPT
# Allow SSH only via USB and Wifi-AP (change port 22 to your SSH port):
ip6tables -A INPUT -i wlan0 -p tcp --destination-port 22 -j ACCEPT
# Allow TCP/IP to do three-way handshakes:
ip6tables -I INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
# Allow loopback traffic:
ip6tables -I INPUT -i lo -j ACCEPT
# Reject all access from anywhere else:
ip6tables -P INPUT DROP
# Block HTTPS advertisements to improve blocking ads that are loaded via HTTPS and also deal with QUIC:
ip6tables -A INPUT -p udp --dport 80 -j REJECT --reject-with icmp6-port-unreachable
ip6tables -A INPUT -p tcp --dport 443 -j REJECT --reject-with tcp-reset
ip6tables -A INPUT -p udp --dport 443 -j REJECT --reject-with icmp6-port-unreachable
# Block Ping Requests:
ip6tables -A INPUT -p icmp -j DROP
# Save ip6tables
netfilter-persistent save
This script will flush all your IPv4 firewall rules:
sudo nano Script/iptables/flush-iptables.sh
Insert:
#bin/sh
# Accept all traffic first to avoid ssh lockdown via iptables firewall rules #
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
# Flush All Iptables Chains/Firewall rules #
iptables -F
# Delete all Iptables Chains #
iptables -X
# Flush all counters too #
iptables -Z
# Uncomment to flush and delete all nat and mangle #
#iptables -t nat -F
#iptables -t nat -X
#iptables -t mangle -F
#iptables -t mangle -X
#iptables iptables -t raw -F
#iptables -t raw -X
# Save iptables
netfilter-persistent save
The same for IPv6:
sudo nano Script/iptables/flush-ip6tables.sh
Insert:
#bin/sh
# Accept all traffic first to avoid ssh lockdown via iptables firewall rules #
ip6tables -P INPUT ACCEPT
ip6tables -P FORWARD ACCEPT
ip6tables -P OUTPUT ACCEPT
# Flush All Iptables Chains/Firewall rules #
ip6tables -F
# Delete all Iptables Chains #
ip6tables -X
# Flush all counters too #
ip6tables -Z
# Uncomment to flush and delete all nat and mangle #
#ip6tables -t nat -F
#ip6tables -t nat -X
#ip6tables -t mangle -F
#ip6tables -t mangle -X
#ip6tables iptables -t raw -F
#ip6tables -t raw -X
# Save ip6tables
netfilter-persistent save
Make all scripts executable:
sudo chmod +x Script/iptables/iptables.sh
sudo chmod +x Script/iptables/ip6tables.sh
sudo chmod +x Script/iptables/flush-iptables.sh
sudo chmod +x Script/iptables/flush-ip6tables.sh
Finally, to enable your firewall run these two commands:
sudo sh Script/iptables/iptables.sh
sudo sh Script/iptables/ip6tables.sh
View current iptables routing rules:
sudo iptables -t nat -v -L -n --line-number
sudo ip6tables -t nat -v -L -n --line-number
View current iptables rules:
sudo iptables -L -n -v
sudo ip6tables -L -n -v
If you are connected to a public Wifi, the service provider may log your devices MAC address and its hostname. Over time this information can be used to profile and to track you. If you are using a VPN, the service provider won't be able anymore to see which websites you visit - only that you use a VPN. To further anonymize our Privacy Gadget we decided to spoof its MAC address with every reboot. Further we wrote a short script that picks a random word from a dictionary as a hostname during each reboot.
Download macchanger:
sudo apt install macchanger -y
IMPORTANT!
During the installation process: select <NO> when asked if macchanger should automatically generate new MAC addresses. We will set up a system service that does this job better:
sudo nano /etc/systemd/system/spoofmac@.service
Insert:
[Unit]
Description=changes mac for %I
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
ExecStart=/usr/bin/macchanger -r %I
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Now we enable the System Service to individually randomize the MAC Addresses of all Wifi-Cards and your ethernet interface:
sudo systemctl enable spoofmac@wlan0.service
sudo systemctl enable spoofmac@wlan1.service
sudo systemctl enable spoofmac@eth0.service
First we download a dictionary and move it to the required location:
wget http://gwicks.net/textlists/ukenglish.zip
unzip ukenglish.zip
rm ukenglish.zip
sudo mv ukenglish.txt /usr/share/dict/
Create a script that randomized the hostname:
sudo nano /root/hostname.sh
Insert:
#!/bin/bash
# Random Hostname Generator
ALL_NON_RANDOM_WORDS=/usr/share/dict/ukenglish.txt
non_random_words=`cat $ALL_NON_RANDOM_WORDS | wc -l`
NEW_HOSTNAME=$(WORD=`od -N3 -An -i /dev/urandom |
awk -v f=0 -v r="$non_random_words" '{printf "%i\n", f + r * $1 / 16777216}'`
sed `echo $WORD`"q;d" $ALL_NON_RANDOM_WORDS
let "X = X + 1")
# Change Static Hostname
hostnamectl set-hostname $NEW_HOSTNAME
head -n -1 /etc/hosts > /etc/tmp
mv /etc/tmp /etc/hosts
echo -e "127.0.1.1 $NEW_HOSTNAME" >> /etc/hosts
Make this script executable:
sudo chmod +X /root/hostname.sh
Then we create a System Service that runs our script each time you boot up the RaspberryPi:
sudo nano /etc/systemd/system/hostname.service
Insert:
[Unit]
Description=Random Hostname
Wants=network-pre.target
Before=network-pre.target
[Service]
ExecStart=/bin/bash /root/hostname.sh
[Install]
WantedBy=multi-user.target
Finally enable the service:
sudo systemctl enable hostname.service
We use a dynamic message of the day to display system information once we log into our Privacy Gadget via ssh.
To set up dynamic motd run the following commands:
cd /etc/update-motd.d
sudo touch 00-header && sudo touch 10-sysinfo && sudo touch 90-footer
sudo chmod +x /etc/update-motd.d/*
sudo rm /etc/motd
sudo rm /etc/update-motd.d/10-uname
sudo ln -s /var/run/motd /etc/motd
We use figlet to display our hostname:
sudo apt install figlet -y
Next edit:
sudo nano /etc/pam.d/ssh
Insert:
session optional pam_motd.so motd=/run/motd.dynamic
# session optional pam_motd.so noupdate
Now we create the dynamic motd header:
sudo nano /etc/update-motd.d/00-header
Insert:
#!/bin/sh
[ -r /etc/lsb-release ] ; /etc/lsb-release
if [ -z "$DISTRIB_DESCRIPTION" ] ; [ -x /usr/bin/lsb_release ]; then
# Fall back to using the very slow lsb_release utility
DISTRIB_DESCRIPTION=$(lsb_release -s -d)
fi
echo "--------------------------------------------------------------------------------"
printf "\n"
figlet $(hostname)
printf "* %s (%s).\n" "$DISTRIB_DESCRIPTION" "$(uname -rm)"
printf "\n"
echo "--------------------------------------------------------------------------------
..
.ckdl' .oKO;
.kWMMKxxkkkxkXMWd.
. .:OWMMMWNXKXXNMMW0l.
,k0d. ;OWMNKkl;'....,cdKWWKo..'coo'
,0WWk. .dXMNx,. .lKMWK0NMWXc
.;kWMW0kXWW0: .;cl;. ,0MMWKd:.
.'. .lOXWMMMWWNKkc. .xNMMWO' :XMNl
oXNKOxxXMWKxlc::;'. 'OWMMMK; '0MWo
'lx0XWMMXo. .. 'oxkd, ,KMWx.
.cXMWo .'. .cOKKOl. .xWMMNKkd;.
,KMNc ,ONXo. '0MMMMK, 'kWMXkk0XW0'
.kWMO' 'xK0c ,dkkd; .lKMWO, ..'.
,0MWKl. .. 'oKWMXo.
.:xXMMMWKxc,. .':oONMMMMK;
'OMWXOdokXWMNKOkdolllllooxOKNWMN0dlkWMK;
,c:. .:o0WMMWWWMMMMMMMNKkdc,. .dXXl
' .dWMKc,;;;l0WMM0; ..
;KMNl ,d0MWx.
.ld:. 'ox:.
--------------------------------------------------------------------------------"
Below the header we insert some system information:
sudo nano /etc/update-motd.d/10-sysinfo
Insert:
#!/bin/bash
date=`date`
load=`cat /proc/loadavg | awk '{print $1}'`
memory_usage=`free -m | awk '/Mem:/ { total=$2; used=$3 } END { printf("%3.1f%%", used/total*100)}'`
processes=`ps aux | wc -l`
swap_usage=`free -m | awk '/Swap/ { printf("%3.1f%%", $3/$2*100) }'`
temperature=`/usr/bin/vcgencmd measure_temp | cut -c "6-9"`
time=`uptime | grep -ohe 'up .*' | sed 's/,/\ hours/g' | awk '{ printf $2" "$3 }'`
echo
echo "System Information: $date"
echo
printf "\e[1;36mSystem Load:\t%s\t Memory Usage:\t%s\n" $load $memory_usage
printf "Processes:\t%s\t Swap Usage:\t%s\n" $processes $swap_usage
printf "CPU Temp.:\t%s°C\t System Uptime:\t%s\n\e[0m" $temperature "$time"
echo
Finally we create the motd footer:
sudo nano /etc/update-motd.d/90-footer
Insert:
#!/bin/sh
[ -f /etc/motd.tail ] ; cat /etc/motd.tail || true
echo "--------------------------------------------------------------------------------"
Further we edited a publicly available .bash_profile to display information related to VPN connectivity status, Wifi-AP, external IP-Address. etc. once we log into our Privacy Gadget via ssh. Further we added an Alias that allows you to switch your Wifi-AP on and off with two simple commands: ap-on and ap-off. Here you can insert your own Aliases as shortcuts to more complex commands.
sudo nano .bash_profile
Insert:
#!/bin/sh
# GWII (global web interface info)
if [ -s ~/.bashrc ]; then
source ~/.bashrc;
fi
#ALIASES:
# Wifi-AP
alias ap-on="if ! ifconfig wlan0 &> /dev/null; then printf '\nWifi-AP Disconnected! Please attach the required USB Dongle...\n\n'; else sudo systemctl start hostapd.service; fi"
alias ap-off="if ! ifconfig wlan0 &> /dev/null; then printf '\nWifi-AP Disconnected! Please attach the required USB Dongle...\n\n'; else sudo systemctl stop hostapd.service; fi"
protonvpn status > ~/.tmp
if [ "$(head -1 ~/.tmp)" = "Status: Connected" ]; then sed -i -e 's/Status: //g' -e 's/Server: //g' -e 's/Country: //g' -e '2,3d;5,7d;9,12d' ~/.tmp; fi;
if [ "$(head -1 ~/.tmp)" = "Status: Disconnected" ]; then sed -i -e 's/Status: //g' -e '2 c\ ' -e '3 c\ ' ~/.tmp; fi
if [ "$(head -1 ~/.tmp | cut -c -3)" = "[!]" ]; then sed -i -e '1 c\ERROR' -e '2,12d' ~/.tmp && echo -e "\n \n " >> ~/.tmp; fi
echo
echo " .~~. .~~. $(tput setaf 1)VPN................: $(head -1 ~/.tmp) ($(sed '3q;d' ~/.tmp) : $(sed '2q;d' ~/.tmp))";
echo "$(tput setaf 2) '. \ ' ' / .'$(tput setaf 1)";
echo " .~ .~~~..~. IP Addresses.......: usb0 `ip -4 addr show usb0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'`";
echo " : .~.'~'.~. : eth0 `ip -4 addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'`";
echo " ~ ( ) ( ) ~ wlan0 `ip -4 addr show wlan0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'`";
echo "( : '~'.~.'~' : ) wlan1 `if [ "$(cat /sys/class/net/wlan1/operstate)" = "dormant" ]; then printf Dormant; elif [ "$(cat /sys/class/net/wlan1/operstate)" = "down" ]; then printf Down; elif [ "$(cat /sys/class/net/wlan1/operstate)" = "up" ]; then printf %s "$(ip -4 addr show wlan1 | grep -oP '(?<=inet\s)\d+(\.\d+){3}')"; fi`";
echo " ~ .~ ( ) ~. ~ ext `if [ "$(cat /sys/class/net/eth0/operstate)" = "up" ]; then printf %s "$(dig +short myip.opendns.com @resolver1.opendns.com 2>/dev/null)"; elif [ "$(cat /sys/class/net/wlan1/operstate)" = "dormant" ]; then printf Disconnected; elif [ "$(cat /sys/class/net/wlan1/operstate)" = "down" ]; then printf Disconnected; elif [ "$(cat /sys/class/net/wlan1/operstate)" = "up" ]; then printf %s "$(dig +short myip.opendns.com @resolver1.opendns.com 2>/dev/null)"; fi`";
echo " ( : '~' : )";
echo " '~ .~~~. ~' Wifi-AP............: `if [ $(systemctl is-active hostapd) = 'active' ]; then printf Connected; else printf Disconnected; fi` (wlan0 : OctoBaer)";
echo " '~' Wifi-AP............: ap-on/off";
echo
echo
printf "\e[0;32m--------------------------------------------------------------------------------\n"
echo
rm ~/.tmp
A simple banner that warns against unauthorized access:
sudo nano /etc/issue.net
Insert:
/ Unauthorized access to this machine is prohibited /
################################################################################
# #
# Welcome... #
# ...all connections to this machine are monitored and recorded... #
# #
# Disconnect IMMEDIATELY unless you are AUTHORIZED! #
# #
# #
################################################################################
/ Unless authorized you will be disconnected shortly /
If you want to make sure that all your internet traffic is only routed through your RaspberryPi Privacy Gadget, we recomend you disable your Mac's Wifi on boot (you can always switch it on manually). This cannot be done via your Mac's System Settings. Your Mac will always automatically switch on your Wifi and try to connect to known networks. This is why we need to configure a startup deamon on our Mac that switches off Wifi before it can try to connect to known networks.
On your Mac, open a Terminal window and type the following command:
sudo nano /Library/LaunchAgents/off.networksetup.plist
Insert:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>off.networksetup</string>
<key>LaunchOnlyOnce</key>
<true/>
<key>ProgramArguments</key>
<array>
<string>networksetup</string>
<string>-setairportpower</string>
<string>en0</string>
<string>off</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
At last we set file ownership and permissions:
sudo chown root:wheel /Library/LaunchAgents/off.networksetup.plist
sudo chmod 644 /Library/LaunchAgents/off.networksetup.plist
You do not need to load this daemon now. If you do, it will switch off your Mac's Wifi adapter immideately. From now on, will be loaded automatically during each reboot. However, if you want to try it out, execute the following command:
sudo launchctl load /Library/LaunchAgents/off.networksetup.plist
We are planning to create a simple web interface that makes it easy for you to connect to new Wifi-Networks, block and allow IP-Address Ranges with an ASN_IPFire_Script. etc.
Copyright (c) 2022 term7
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.