Does anyone know the best way to route traffic from transmission through Mullvad?
I have transmissionset up on my plex server which I control using tranmission remote and want to download my Linux ISOs with privacy.
I have downloaded the wireguard config and can connect to it using wg-quick, but I don’t want all traffic going through it, only transmission.
I personally shove Transmission into Docker:
services: wireguard: image: ghcr.io/linuxserver/wireguard container_name: wireguard cap_add: - NET_ADMIN - SYS_MODULE environment: - PUID=1000 - PGID=1000 - TZ=Europe/Stockholm ports: - 9091:9091/tcp volumes: - ./config:/config - /lib/modules:/lib/modules sysctls: - net.ipv6.conf.all.disable_ipv6=0 - net.ipv4.conf.all.src_valid_mark=1 restart: unless-stopped transmission: image: ghcr.io/linuxserver/transmission container_name: transmission ulimits: nofile: 1048576 environment: - PUID=1000 - PGID=996 - TZ=Europe/Stockholm - USER=azurediamond - PASS=hunter2 volumes: - ./config:/config - /data:/data - /data/Torrents/dl:/downloads - /data/Torrents/inbox/start:/watch network_mode: "service:wireguard" depends_on: [ "wireguard" ] restart: unless-stoppedMake sure your mullvad config is called
wg0.confin./config.I do this except with https://github.com/qdm12/gluetun
(which apparently also can be used as a k8s sidecar container, am gonna try this soon as well)
Oh yes, got your password :p
All I see is *******.
Really?
Password: ********
h2
I’m trying this and it seems to be running. If I run
curl 127.0.0.1:9091I get a 403 which is expected but if I try to access the same from another computer on the network then the connection times out, any idea what could be the cause?
Consider moving from mullvad if you are into torrenting. Mullvad doesnt support port forwarding anymore. But no matter what provider you chose, use docker container gluetun to route traffic from any other container (like transmission). I like transmission, but most people use qbittorrent because its more advanced. You can also set up VPN in qbittorrent settings
Which affects torrentors how?
If the port you’re connecting through isn’t forwarded, it isn’t allowing most connections through, drastically slowing down your speed and ability to seed, since you can’t connect to any peers.
I don’t torrent, as a rule, so I can’t say I’d notice any speed reduction. I had, however, noticed that no matter how long I kept seeding, I’d gotten few - or maybe no - connections. I didn’t know if this were because nobody else was leeching the thing at the time, or something else like this.
I’m very reluctant to give up Mullvad. So far, in all ways I care about they’ve demonstrated justification for brand loyalty. Plus, I’ve been with them for years and already have everything set up and configured across multiple deviiiiceeeessss.
As I said, torrenting isn’t a critical activity for me, so I’ll hang tight. I am curious to know if Mullvad has given a justification for stopping support for port forwarding. They used to, right? So it was work for them to stop.
Here is their blog post about it: https://mullvad.net/en/blog/2023/5/29/removing-the-support-for-forwarded-ports/
Thank you for the link! Very informative.
You’ll get more connections if people can get to you; otherwise, you’re only connecting to people who are port forwarding themselves. If you’re port forwarding, you can connect to everyone.
I highly recommend moving that to a docker or podman setup. Gluetun is the go-to for VPN traffic. Set up a little container and you can link other containers to it to route all their traffic through.
The best way I’ve found.
You might want your program and the vpn interface to be in a separate namespace? Somewhat opposite this: https://www.wireguard.com/netns/#the-new-namespace-solution
You don’t want all traffic routed, you want only this one app. More info here: https://linuxhint.com/use-linux-network-namespace/
This is a great solution!
Also saw this now: https://slrpnk.net/post/2096570
Mullvad is using WireGuard though
Mullvad also offers open VPN
Not on most servers
They have different servers for open VPN. But they exist in most cities.
https://github.com/Safing/portmaster
You could use something like portmaster to route only that program to the VPN.
Probably safer to configure your program to use the mullvad proxy. That way if mullvad is offline it just won’t work.
The gold standard for what you want to do is qubes, where you would set up a VM that can only talk to a VM that’s routing to the VPN. But that’s a lot of work. You might be able to set something similar with containers.
This other post may be interesting as well https://slrpnk.net/post/2096570
How do I configure it to use the Mullvad proxy?
I would Google transmission proxy configuration
You don’t, Transmission does not have proxy support. It was intentionally removed a while back & currently the devs have no plans to re-implement it e.g. https://github.com/transmission/transmission/issues/1375
Just use a VPN connection like others said.
If transmission is running in a container, my latest blog post is actually about that: https://www.nicoco.fr/blog/2023/09/10/wireguard/
deleted by creator
