I’m using OpenClash in my router to make shit version of Tor network. I’m using 4 different VPSs to access the internet. It is wonderfull to be able to tell which connection go through what site, or using all of those VPSs to access the internet simultaneously using load-balance method.
I love it.
However, I have a problem. Since it is rule based, I dont know what IPs or ports do torrent connections use. It sometime used Direct (from my ISP) connection which scared me.
Clash sounds interesting. How to manage depends on clash rule options and management features.
By default, most torrent clients will open random outgoing ports on the default interface. For the listen port, it will be opened locally and they will try to open an incoming port with upnp
Probably the most suitable client for this is qbittorrent. You can assign a specific network interface and incoming and outgoing ports.
You could create a virtual network interface just for your client. Tag it with VLAN for easy management by clash.
You could definitely collect the ip addresses of the most common trackers, but it would be impossible to collect the ip addresses of all possible peers.
It is. I believe it’s one of the best thing I install on my homeserver. All my family members are now using VPN, and have their tracker and ad blocked. Since I’m the one who managed the VPS, I can just destroy all the data in it in case anything went wrong.
So, can I open only one port on my torrent app and have all the incoming connections go through it? That’s neat. Clash supports port redirection, and I think I’ll use that feature. I will give you update.
I found this anime-trackers project on github, but it doesnt help, lol.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Clash sounds interesting. How to manage depends on clash rule options and management features.
By default, most torrent clients will open random outgoing ports on the default interface. For the listen port, it will be opened locally and they will try to open an incoming port with upnp
Probably the most suitable client for this is qbittorrent. You can assign a specific network interface and incoming and outgoing ports.
You could create a virtual network interface just for your client. Tag it with VLAN for easy management by clash.
You could definitely collect the ip addresses of the most common trackers, but it would be impossible to collect the ip addresses of all possible peers.
It is. I believe it’s one of the best thing I install on my homeserver. All my family members are now using VPN, and have their tracker and ad blocked. Since I’m the one who managed the VPS, I can just destroy all the data in it in case anything went wrong.
So, can I open only one port on my torrent app and have all the incoming connections go through it? That’s neat. Clash supports port redirection, and I think I’ll use that feature. I will give you update.
I found this anime-trackers project on github, but it doesnt help, lol.