diff options
author | jwansek <eddie.atten.ea29@gmail.com> | 2024-12-22 17:12:18 +0000 |
---|---|---|
committer | jwansek <eddie.atten.ea29@gmail.com> | 2024-12-22 17:12:18 +0000 |
commit | 2b0d0820da6370baa184c823a4a55ee07496f179 (patch) | |
tree | 0b7074787dd4ebbe5298fca44329cd62da73a23d | |
parent | 569deda4691cfb92e4c199a0a2431dfb5e6680d3 (diff) | |
download | TrueNASTorrentingStack-2b0d0820da6370baa184c823a4a55ee07496f179.tar.gz TrueNASTorrentingStack-2b0d0820da6370baa184c823a4a55ee07496f179.zip |
Added README.md
-rw-r--r-- | README.md | 20 |
1 files changed, 18 insertions, 2 deletions
@@ -1,2 +1,18 @@ -# TrueNasTorrentingStack -Use macvlans to bind docker containers to a single address +# TrueNASTorrentingStack +Use `macvlan`s to bind docker containers to a single address. + +When torrenting we typically want to hide our real IP address so our ISP doesn't get mad at us. +I have a VLAN, set up in pfsense, that routes through wireguard to an AirVPN VPN, thus hiding my +real ip address to anything connected to this network. This VLAN is set up as `br23` on my TrueNAS. +It uses the IP range `192.168.23.1/24`. + +Back in the TrueNAS Core days, we could easily route FreeBSD Jails through a single interface, in the web UI. +We could even use DHCP. TrueNAS Scale does away with Jails and uses docker instead. +In docker we can do something similar with `macvlan`s to allow our containers to get a new IP address routing +through a given network. Unfortunately we can't get DHCP addresses from our router, everything has to be set +to static. + +Sadly, as of TrueNAS Scale Electric Eel, and apparently Fangtooth too, this is not possible in the web UI. +[Which has annoyed a lot of people.](https://forums.truenas.com/t/allow-apps-to-have-their-own-ip/12042) +This is how I have achieved it, using docker-compose. + |