![]() I looked into setting the network interface, and deluge does have the same option! I was able to verify with ifconfig that while the vpn is connected, I have a network interface named nordlynx. I'm not sure if there's any significance there, but I wanted to make note of it. There wasn't anything about disabling IPv6 at the OS level in the tutorial for installing nordvpn. I do think I should note that I found the link to that page while reading Nord VPN's tutorial for setting up OpenVPN on linux, however I'm using nordvpn/nordvpnd to handle the VPN connection. Thanks for the reply! Yes, that's the tutorial I followed this morning, so I haven't tested it, yet. I downloaded a torrent that would definitely attract attention if my IP was leaking, and I haven't heard shit. Thanks u/pennyhoard20 for all your help!ĮDIT: looks like this config is working. Why in the hell would it want the name of interface for outgoing and the IP address of the interface for incoming is beyond me, but _I believe_ I've got this properly set up now. I assumed this was meant to be the IP address of my VPN server or possibly the name of the interface, and couldn't get it to work, but _finally_ I noticed the tool tip said that it was supposed to be the _address of the interface_. I'm not concerned with this, because nordvpn can whitelist local subnets which allows me to connect to my home server.). messing with route tables, so only deluge used the VPN. But "Incoming Address" was less clear, and I had hard time findingp any recent details on it, aside from people trying to do a much more complex setup that I was (i.e. It just wants the name of your VPN's network interface, `nordlynx` in my case. "Outgoing Interface" is very straight forward. ![]() So, after a shit ton of Googling and finally noticing a helpful tool tip in the GTK client, _I think_ I was able to figure out exactly what deluge is expecting for the "Incoming Address" and "Outgoing Interface" settings. ![]() In light of this, I decided to risk deluge's worse UX and less than stellar documentation. However, from what I've been able to find, while qB can be run as a daemon on a home server, it seems that it doesn't have an official thin client mode like deluge does (I'd be happy to find out I'm wrong about this). It seems to have a much more intuitive and less opaque configuration. u/pennyhoard20 suggested to use qBitorrent, and I think that's probably the best recommendation for most users. The main issue is that I needed to configure my client to only use the network interface tied to my vpn, which with nordvpn in linux and NordLynx technology enabled is named `nordlynx`. This likely explains why I still got DCMAs while nord reported solid uptime. I was relying on nordvpn's kill switch, and from what they linked me to and what I found Googling myself, kill switches aren't reliable. U/pennyhoard20 was a great help in understanding what was actually going wrong. I'll update this post with whether or not I actually did it properly (i.e. Wanted to share what I landed on since I had a pretty hard time figuring out how to configure deluge to safely use a VPN. # Settings before my last DCMA Technology: NORDLYNX Any help or advice would be greatly appreciated. If I'm downloading from a honeypot, they should only see my VPN's IP, or at least, that's how I understand it. I don't think anything is being downloaded to my PC, and even if it was, only the torrent site(s) (1337x and Pirate Bay) should be able to know my actual IP. Though, I can't imagine how this would be the problem, because I have my deluge client connected to the server and I'm using magnet links. The only other important note I can think of is that I am using another computer which is not on the VPN to add torrents. Set up a proxy in deluge following this tutorial. Set DNS servers to Google's DNS (Maybe there's some better options?). Disabled IP v6 on the server (Though, I think the `nordvpn` daemon was already effectively disabling it). Since the last email, I've done a few other things, though I'm not sure how effective they will be at keeping my traffic hidden. I've since changed a few things, but my settings as of my last DCMA email are listed below. I'm really not sure how they're tracking me. ![]() I've checked with and other services to ensure that my Cox IP isn't being leaked, and it looks fine. However, I'm still getting DCMA emails from Cox. I've got Ubuntu 22.04 running with deluged and nordvpn. Hi, I've fairly recently set up what I thought would be a secure home server for torrenting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |