this post was submitted on 07 Dec 2023
55 points (98.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54609 readers
710 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] tuff_wizard@aussie.zone 9 points 11 months ago (2 children)

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

[–] Rizoid@programming.dev 7 points 11 months ago (1 children)

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@aussie.zone 3 points 11 months ago

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.