How to make sure transmission is using my vpn?

I have transmission running on my server in a docker container that is supposed to go through gluetun. If I run test with ipleak and other torrent ip testers it shows my vpn’s ip address. However transmission is running way faster download speeds than deluge or qbit were with the same configuration. It makes me wonder if all the traffic isn’t going through the vpn somehow and I can’t think of any other way to check things other than ipleak tests. I’m probably being over paranoid but a few months ago qbit leaked and I got a letter from my isp. I really don’t need that happening again. Any help would be appreciated.

rambos,

You need gluetun! It supports almost all VPN providers

ben, (edited )
@ben@lef.li avatar

Use a firewall to block all outgoing packages through all interfaces but lo and tun (or wg for Wireguard). Like this for iptables:


<span style="color:#323232;">-A FORWARD -j REJECT --reject-with icmp-port-unreachable
</span><span style="color:#323232;">-A OUTPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
</span><span style="color:#323232;">-A OUTPUT -o lo -j ACCEPT
</span><span style="color:#323232;">-A OUTPUT -d 1.2.3.4/32 -p udp -j ACCEPT </span><span style="font-style:italic;color:#969896;">#replace with public IP of your VPN you try to connect
</span><span style="color:#323232;">-A OUTPUT -p icmp -j ACCEPT
</span><span style="color:#323232;">-A OUTPUT -o tun+ -j ACCEPT </span><span style="font-style:italic;color:#969896;">#replace with wg+ for Wireguard
</span><span style="color:#323232;">-A OUTPUT -j REJECT --reject-with icmp-port-unreachable
</span>

If you are paranoid you could mess with INPUT table as well but if OUTPUT is configured properly nobody well ever know your real IP address.

Not sure how well this works with Docker and such, I use LXC containers.

The funny thing is that I am actually seeding Linux ISOs (yes, real ones). The reason I am using a VPN to seed those is because the ISP is complaining about random peers hitting (non-existing obviously) addresses in private IPv4 ranges (like 172.16.1.1) and instead if simply dropping those packages at the switch … oh well. I guess some people have multiple peers connected to each other via private networks but external peers don’t know about these connections and simply try to reach them on their private addresses over public internet.

Anyway yeah I could mess with routing table on my server and null-route those ranges but I have an active VPN contract already so why not using it?

Imprint9816,

Turn your vpn off, if transmission keeps downloading it’s not setup properly.

anothercatgirl,

yes and there are safe files to torrent like Linux ISOs, can test with those

jol,

Isn’t it only dangerous hackers who download Linux?

jaykay, (edited )
@jaykay@lemmy.zip avatar

Only if it’s Arch… or Kali

jol,

I think that’s for hormosexuerls no? No thank you.

UmbraTemporis,

I feel attacked

LSNLDN,

Good attitude man fuck a homerseksual

kniescherz,

Use docker with a container which can only go online thru a vpn like transmission-vpn.

starlord2014,

You can open a consol log for the transmission container and type “curl ifconfig.io”. This will return you wanip. Compare that to what you were expecting.

jacksilver,

There are sites like this (www.whatismyip.net/tools/…/index.php?hash=1b0ed88…) that let you download a torrent. When you run the torrent in the client the site tells you the IP of your torrent client. Based on that info you can tell if it’s running through the VPN or not.

xilliah,

You’ll receive a letter to remind you.

tuff_wizard,

Can you just give gluetun the wrong info for you vpn server and see if transmission still works?

Rizoid,

So this worked and I was unable to use transmission without gluetun connecting properly. Is it normal for some clients to just be faster with the same torrents? Like about was at like 1-2mib and transmission with the same torrent is running at 4-5.

tuff_wizard,

No idea but there are new and exciting torrent technologies being worked on all the time. Things like DHT nodes or turning off anonymous mode can affect speeds. Your other clients may have different settings enabled or disabled or may not have implemented new protocols.

Illecors,

Packet sniffing.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • piracy@lemmy.dbzer0.com
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #