Container-based Tor access point (Anonymizing Middlebox).
How it works
Tor Box is a script for Setting up a Tor wireless access point using docker containers. it's aimed to be used as an Always-On anti-censorship BACKUP gateway. This script enables you to directly route traffic of connected devices to the Tor network Currently Tor Box only supports IPv4, and only traffic from TCP/DNS/DHCP is allowed any non-local traffic from other protocols are blocked. this script is not optimized for visiting .onion addresses. please use Tor Browser instead. Tor Box is to be used only as a BACKUP for situations where popular solutions (such as OpenVPN) are temporarily blocked by a state firewall. This isolation is achived by sharing a Network Namespace between the containers.
- wireless network card/adapter (with proper drivers already installed).
- following packages must be installed:
templates/torrc.template according to your needs but do not touch
- Debian 10 with RT5370 Wireless Adapter
- Raspberry Pi 3
git clone https://github.com/itshaadi/torbox.git cd torbox chmod +x torbox
./torbox help Usage: <start|stop> <interface> <log> <container> eg: ./torbox start wlan0 ./torbox log torbox-tor ./torbox stop wlan0
sudo nmap -sU -p 10558 220.127.116.11 # us1.freeopenvpn.org (non-local UDP connection is dropped) Starting Nmap 7.80 ( https://nmap.org ) at XXXXXX Nmap scan report for 18.104.22.168 Host is up (0.00085s latency). PORT STATE SERVICE 10558/udp filtered unknown sudo nmap -sU -p 5353 192.168.162.1 # DNS (which uses UDP) is allowed Starting Nmap 7.80 ( https://nmap.org ) at XXXXX Nmap scan report for 192.168.162.1 Host is up (0.00053s latency). PORT STATE SERVICE 5353/udp open zeroconf MAC Address: XXXXXXXX (Tenda Technology)
Filtered means that a firewall, filter, or other network obstacle is blocking the port so that Nmap cannot tell whether it is open or closed. source