@TCB13@lemmy.world
@TCB13@lemmy.world avatar

TCB13

@TCB13@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

TCB13,
@TCB13@lemmy.world avatar

I just don’t want my content scattered across different platforms in suboptimal quality and be forced to pay

That and also the fact that sometimes content vanishes from those platforms because of licensing agreements and/or get censored like many older TV Shows have gotten.

How do y'all deal with programs not supported on Linux?

I’ve been seeing all these posts about Linux lately, and looking at them, I can honestly see the appeal. I’d love having so much autonomy over the OS I use, and customize it however I like, even having so many options to choose from when it comes to distros. The only thing holding me back, however, is incompatibility issues....

TCB13,
@TCB13@lemmy.world avatar

Look at my screenshot above. Do you call that “looked exactly as intended”?

Favourite FOSS Torrenting Client for Linux that has a VPN killswitch?

I’m a long-time Transmission user but I just learned that VPN killswitches are a thing (how did it take me so long!?). I would like to try another client which has this feature in case I forget to launch my VPN client before opening Transmission. Does anybody have any recommendations? Deluge? QBittorrent? Or any others?...

TCB13,
@TCB13@lemmy.world avatar

There’s a simpler option for those who like Transmission: lemmy.world/comment/5269089

TCB13,
@TCB13@lemmy.world avatar

True, but enforcing the restriction at the systemd level will be safer. Frankly I like Transmission.

TCB13,
@TCB13@lemmy.world avatar

Yes it can get better :P lemmy.world/comment/5269089

TCB13, (edited )
@TCB13@lemmy.world avatar

you’ll need to reconfigure Transmission with the new IP. Sure your method works for a kill switch. But it requires manual intervention every time it gets killed.

It doesn’t. You can specify your VPN provider range instead of a single IP and you won’t need manual intervention.

If you go the systemd route you can do it even better with RestrictNetworkInterfaces:

RestrictNetworkInterfaces= Takes a list of space-separated network interface names. This option restricts the network interfaces that processes of this unit can use.

So I guess this is a better option than doing IP or IP range restrictions - zero manual intervention like you do in qBit. I’m so used to work with IPs instead of interfaces (because of the issues that can cause) that I even forgot about that option.

TCB13,
@TCB13@lemmy.world avatar

Forget about those, for 100$ you can get a second hand HP Mini that has a full i5 8th gen CPU and 16GB of RAM. Way better in all possible ways. Those systems also run very well with Linux.

TCB13, (edited )
@TCB13@lemmy.world avatar

If you’re running Transmission on Linux know that I can be set to only use the VPN IP, there’s also another good way to implement a kill switch: lemmy.world/comment/5269089

TCB13,
@TCB13@lemmy.world avatar

Not sure that transmission supports it

Yes transmission does support it, however if you’re running in Linux you can also just restrict it to run on the VPN IP or interface. Read more here: lemmy.world/comment/5269089

TCB13,
@TCB13@lemmy.world avatar

Here: lemmy.world/comment/5269089

TCB13,
@TCB13@lemmy.world avatar

In you case setting bind-address-ipv4 and bind-address-ipv6 to your VPN IPs should work. According to this under macOS settings are stored in $HOME/Library/Preferences/org.m0k.transmission.plist. Not sure if the format is the same tho and don’t forget that editing a plist on macOS isn’t just always just editing a text file, it might be encoded and cached by the system, do your research.

TCB13,
@TCB13@lemmy.world avatar

Well Facebook tried that.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #