http://grimore.i2p/networking/routing_packets_through_socks_proxies_via_packet_mangling?i2paddresshelper=XeeEcrjZBSZvLCLt32HWWojBguqcQNIfCcYnLhCSpV3LHMHvq-3nkdVw3DGoJYEQnLEpbhLEH~KwUXs42auWcbRedx895ciACwHpMBnchqCYvYeqKNOnMnlZkpSGJNNSRXAcUM48WLh7v6PscDCDKQFN8KVo9n6OBm0KKQjmaQjIN3unappXVvN90d0Q6tWjftn1mTtm2Is4sYYM3glXr47IXPjTha~XW6Ex5wNqtD7pR5rNN5g5Xcpww2teT~mo52Z1xFE5g7ZgK3rHRVnShmolLNwU2VT1ZGqI5X74Tq6DPu6itln3SYyF6db-X
Now, to check that the table tor1 contains the desired routing decisions, issue: ip route show table tor1 which should output something similar to: default via 169.254.1.2 dev tor1 The systemd service file, performs the following operations in order: create a TUN interface named tor1 , bring the TUN interface up, assign the IP and netmask address 169.254.1.1/30 to the TUN interface, add a rule that will make packets marked with the identifier 0x32 lookup...