Comment on Proxying torrent traffic to homeserver

• TCB13@lemmy.world ⁨1⁩ ⁨month⁩ ago

  By “set up wireguard to route through the VPS” you mean having wireguard forward a port from the VPS to a port on the homeserver at its wireguard IP address?

  Yes, he means that.

  qBittorrent will still need to publish the right IP address to peers though, right? So I will need to configure the proxy VPS’s IP address in qBittorrent…

  No. For most things qBittorrent does public IP detection. For the rest your VPS will be doing NAT between the WG interface and the public internet. This means your qBittorrent client sends outgoing packets with the source address of your WG private IP and then the VPS will change those to it’s public IP address.

  The thing you must be careful about is that you need to restrict qBittorrent to only send and receive traffic on the WG interface, otherwise it will be using both. You can do it in the settings, but the safest way is to do it at the systemd service level and completely hide any interface that isn’t the WG one from it.

  source

  • andscape@feddit.it ⁨1⁩ ⁨month⁩ ago

    Wow thank you, this is the most useful reply I’ve received so far!

    This means I don’t need to mess around with QBT’s “proxy” settings? I was pretty confused since the only options available are SOCKS/SOCKS5 and HTTP, but I’m guessing that’s a different kind of proxy than what I need…

    source

    • TCB13@lemmy.world ⁨1⁩ ⁨month⁩ ago

      This means I don’t need to mess around with QBT’s “proxy” settings?

      No, you don’t. In short, trackers will look at the source address of the incoming connection on their side, that means you VPS IP because you’re doing NAT on the VPS.

      Just make sure qBittorrent is restricted to the WG interface and nothing else.

      source

      • andscape@feddit.it ⁨1⁩ ⁨month⁩ ago

        Fantastic, thank you

        source