Hello, for my home installation, I’m using a Raspberry Pi with YunoHost installed on it. My server is exposed through a Neutrinet VPN, but I would like to use another VPN, for example Mullvad VPN, for downloads made with Transmission, and only for that, is it possible?

I’m afraid that by installing Mullvad VPN it will take over from the other VPNs, whereas I just want it to be used as a proxy by Transmission.

    • nate3D
      link
      fedilink
      31 year ago

      Save yourself my troubles and go with this suggestion. I’m using this with a few different OpenVPN service providers and it works wonderfully.

      Initially I had tried gluetun + transmission with gluetun acting as a socks5 proxy for the transmission instance but the shadowsocks impl it uses won’t support socks5 from any of the torrent clients I tested with.

      • retiolusOP
        link
        fedilink
        11 year ago

        Hi, thanks all for your suggestions, but I don’t use docker and I don’t want to use docker. I don’t like the “container” aspect of it.

  • @crunchymunchytoast
    link
    31 year ago

    I think your options are mainly virtualization or something like this

    Virtualization is definitely easiest though; there’s a transmission docker image out there that’s preconfigured for a ton of VPN providers, including mullvad. It can be touchy to get working but is amazing when it does work.

    • retiolusOP
      link
      fedilink
      1
      edit-2
      1 year ago

      I didn’t know it was possible to do split tunnelling with the Mullvad cli! I’ll have a look and give my feedback, thanks!

      Edit: Oh, it’s using OpenVPN of course

  • @Reliant1087
    link
    21 year ago

    There is a docker container which has transmission and openVPN. The other option is to use any VPN container such as gluetun and route transmission container’s network through that using docker network mode.

    • mistgate
      link
      21 year ago

      This is what I do but with qbittorrent and ProtonVPN. Just put the port details in the gluetun section and in the qbittorrent section put in network_mode: “service:gluetun”. Works just fine so far for me.

      https://github.com/qdm12/gluetun/wiki/Connect-a-container-to-gluetun

      ---
      version: "2.1"
      services:
        gluetun:
          image: qmcgaw/gluetun
          container_name: gluetun
          cap_add:
            - NET_ADMIN
          devices:
            - /dev/net/tun:/dev/net/tun
          network_mode: bridge
          ports:
            - 8081:8000/tcp # http control
            - 8888:8888/tcp # HTTP proxy
            - 8080:8080/tcp # qBittorrent
            - 9117:9117/tcp # Jackett
          volumes:
            - /docker/gluetun:/gluetun
          environment:
            - VPN_SERVICE_PROVIDER=protonvpn
            - TZ=Europe/London
            - SERVER_COUNTRIES=Netherlands
            - OPENVPN_USER=USERNAME
            - OPENVPN_PASSWORD=PASSWORD
            - HTTPPROXY=on
            - HTTPPROXY_STEALTH=on
            - HTTPPROXY_USER=username
            - HTTPPROXY_PASSWORD=password
          restart: always
      
        qbittorrent:
          image: ghcr.io/linuxserver/qbittorrent
          container_name: qbittorrent
          network_mode: "service:gluetun"
          environment:
            - PUID=1000
            - PGID=100
            - TZ=Europe/London
            - WEBUI_PORT=8080
            - DOCKER_MODS=arafatamim/linuxserver-io-mod-vuetorrent
          volumes:
            - /docker/qbittorrent:/config
            - /srv/mergerfs/downloads/torrents:/downloads
          restart: always