This seems like something that would be simple, but I spent a long time trying to figure it out. I figured I'd write a blog post about it in case anyone else has a similar desire.

all 13 comments

sorted by: hot top controversial new old
[–] 11 points 2 years ago (8 children)

i found it very easy to grab a couple of pre-built containers.. im using deluge and gluetun .. im sure theres a transmission container out there also.

setup your auth info in gluetun, point your deluge/trans container at gluetun for its network and youre done.

  • source
  • hideshow 8 child comments
  • [–] [S] 6 points 2 years ago (4 children)

    I don't know why, but I've always shied away from using docker. This does seem like an area where it would be particularly useful.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 2 years ago (2 children)

    Is this a server or your pc? Docker is kinda silly if it’s just your pc.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (2 children)
  • [–] 3 points 2 years ago

    This is what I use as well, although it was primarily out of laziness. Works well enough. I would say the Gluetun solution is a better recommendation, more robust and scalable, but the haugene container basically just works.

  • source
  • parent
  • [–] 5 points 2 years ago

    Thank you for taking the time to put this together and post it.

  • source
  • [–] 1 point 2 years ago

    Gluetun is the way. Get a transmission docker container, set up a gluetun docker container, set the gluetun container as the network for the transmission container.

    Viola, you have a perfectly working VPN with a kill switch.

  • source
  • [–] 1 point 2 years ago (1 child)

    On BSD you use FIBs to declare process specific routing tables, on Linux you use firewall marks to do the same, then just route all trafik through the vpn uplink and deny any other.

  • source
  • hideshow 1 child comment