Qbittorrent - 2nd Network interface

Apps and Virtualization
1

Hi, my TrueNAS runs on a PC with 2 NICS. I would like to route Qbit traffic trough a VPN. I know it cannot be done in HexOS/TrueNAS directly using the app library, so I’m trying an alternative method via this secondary NIC. I already have:

  1. Added a VPN client to my Unifi controller

  2. Created a separate network/subnet with a rule that all traffic on this subnet goes trough the VPN (x.x.50.x)

  3. Gave my 2nd NIC an address in the new subnet. (x.x.50.118)

  4. TrueNAS and all services are currently accessible via both subnets (x.x.50.118x & x.x.1.118)

Question 1 >> Is there a way that I can tell one app to have all in/outbound traffic (to the internet) go trough the secondary NIC (x.x.50.x118)?

I’ve been playing with the HostIP settings of Qbit in TrueNAS, for both the UI and BT port. Was able to set the UI (and BT) port to the second NIC IP address, which worked okay >> UI moved to .50.118 and was no longer accessible on .1.118, but when I later checked torrent network traffic, it was still coming over the main NIC because of the default gateway route to x.x.1.118.

Question 2 >> I’ve found there is a setting in Qbit itself that allows a “network interface” selection. Settings >> Advanced >> Network interface

image
image607×222 43 KB

So is there is a way to pass-trough the second NIC directly to the app (via the TrueNAS ui), using something like docker network, bride, VLAN, etc? So that I can then select it in Qbit?

I’m still very much a beginner with TrueNAS so any advice is more then welcome…
Thanks!

2

Assigning qbittorrent to the secondary NIC from its own internal settings would likely require you to set the container to run in host network mode, to allow it to see the interface directly, otherwise you’re going through docker’s own networking and routing layer.

3

Nope, all apps use the default system gateway.

4

I was already expecting this to be the case. Is this something that potentially is being re-considered in TrueNAS 26 or 27 ?

5

No, because that’s just how Unix networking works.

Create a VM for your application, pass the NIC through as PCIe device to the VM and your “Linux ISOs” will have their own network stack, separate from all other traffic.

6

Thanks!

Funnily enough that’s how the dataset is actually called :smiley: