Brickfrog @ brickfrog @lemmy.dbzer0.com

Posts

0

Comments

308

Joined

2 yr. ago

For any of this to make a difference you should disable µTP in your torrent client, or make it prefer TCP over µTP.

Just as a caveat, people disabling/throttling µTP may want to manually set appropriate global rate limits (upload/download bandwidth) otherwise it's possible the torrent client will actually hit the maximum upload/download limits of the ISP or router forcing everything else on the network to slow down/time out during other internet usage. You're obviously more advanced so you already know all this :)

Mainly it's extra info for noobs messing around with their settings, often times noobs mess around with settings, disable things, etc. & then wonder why their torrent client keeps "crashing" their internet :P Making changes to µTP should be more of a last resort IMO.

µTP itself is a pretty big topic, there are a fair amount of people testing different settings in the qBittorrent / Libtorrent Github Issues but I'm not sure there's even a consensus on a proper default setting. e.g. qBittorrent's devs specifically chose different µTP defaults vs the Libtorrent library's own defaults. qBittorrent defaults to having µTP enabled with preferring TCP (throttles µTP), Libtorrent defaults to having µTP enabled with peer_proportional (does not throttle µTP). The qBittorrent default is reasonable though I wonder if the Libtorrent default is the more "correct" approach but that's certainly up to much debate. In both cases µTP is never disabled completely.

With my own testing I tend to keep settings at Libtorrent defaults just to observe behavior, with mainly private tracker peers I've noticed at least ~60% of my incoming connections are from µTP peers so at least for me it seems reasonable to keep it enabled.

There's very little info to work with so it's unlikely you'll receive any specific advice.

But mainly you do want to be fully connectable (port forwarded) so check that. Go to any port test website (https://www.canyouseeme.org/, https://www.yougetsignal.com/tools/open-ports/, etc.) and enter your torrent client's incoming connection port there. (for qBittorrent that is in Tools / Options / Connection / Listening Port)

If that test fails then you need to figure out what is blocking your torrent client's incoming connection port.

• If you're using a proxy that's the issue, won't get an incoming connection port via proxy
• If you're using a VPN service that does not support port forwarding then that's the issue, it is impossible to port forward on a VPN without port forwarding support
• If you're using a VPN service with port forwarding support then go to their website & figure out how to configure it, each VPN service is slightly different
• If you're not using a VPN/Proxy then most likely you'll need to log into your network router/firewall & configure a port forward there. Basically create a port forward for your torrent client's incoming connection port & point it to your local system on the network (your NAS)

Also make sure to whitelist your torrent client in any anti-virus/malware software you are using, those will definitely slow you down and/or block connections to your torrent client.

There's potentially other issues but everyone starts with being connectable first.

Your TGx link is broken, I found the correct one at https://torrentgalaxy.to/forums.php?action=viewtopic&topicid=2657 EDIT: Nevermind looks like Lemmy itself keeps breaking the link, try this linked version instead

Sort of related question: Do any of the torrent indexers with DHT crawler currently index Bittorrent V2 hashes? That would seem like the easiest workaround for finding V2 torrents since none of the general public/private sites have V2 support.

(I'm talking about sites like BT4G, BTDig, SolidTorrents, BitSearch, BTMET, Libtor, etc.)

You can double-check but AFAIK that VPN service does not offer port forwarding. It'll probably be even slower than your current VPN service since it's not really meant for torrenting or heavy usage.

Search around for earlier posts on VPNs with port forwarding e.g.

https://lemmy.dbzer0.com/post/2311570

https://lemmy.dbzer0.com/post/969323

https://lemmy.dbzer0.com/post/465513

https://lemmy.dbzer0.com/post/312389

etc.

I would look into port forwarding, but it seems like Mullvad doesn’t support that anymore?

Correct, in your case it is impossible to use any port forwarding until you switch VPN services. In the meantime you're basically stuck with whatever torrent speeds / connectivity you manage to achieve.

Wonder how active the project is, to date they still haven't included the old RARBG torrents.

https://git.torrents-csv.ml/heretic/torrents-csv-data/issues/1

Not anymore

https://mullvad.net/en/blog/2023/5/29/removing-the-support-for-forwarded-ports/

However, the server doesn’t have the best power consumption, so I’d like to use WoL to remotely turn it on.

When you say remotely you mean over the internet, right? Or did you mean remotely within the same LAN e.g. from your living room or wherever.

By default WOL doesn't work over the internet AFAIK. The wikipedia page mentions it a bit https://en.wikipedia.org/wiki/Wake-on-LAN#Subnet_directed_broadcasts

Like others said you may be able to get that going with a VPN or anything VPN-like that allows broadcasts between connected systems. Or if your motherboard supports IPMI / IMM you should be able to connect to the system & perform power functions that way.

In my case my motherboard doesn't have those sort of management functions so in the end I settled on logging into my router remotely & initiated WOL through there. That could be another option for you if your network router is capable of sending WOL packets to the LAN.

However, the server doesn’t have the best power consumption, so I’d like to use WoL to remotely turn it on.

The ads were a Vuze thing, not BiglyBT.

When the devs left Vuze and forked the code into BiglyBT they never included ads or anything like that. That's what the comment meant, that since day 1 of the BiglyBT fork it did not include the ad junk that Vuze has.

Is there anything Jackett does that can’t be manually installed to qBittorrent as a search plugin?

Well yeah, Jackett supports around 585 public/private torrent indexers and trackers. You can view them all on their Github page https://github.com/Jackett/Jackett

AFAIK there are not 585 existing search plugins you can install into qBittorrent so Jackett has way, way more functionality in that sense.

The better question is whether you need all those as search plugins? Probably not, you're likely fine with a few search plugins for the bigger sites.

Tried it out a few years back, it sort of works okay for those looking for something like this. Its interesting feature is the ability to search among other clients running the same software so it's a sort of distributed search. To do that I think it has to advertise the torrents you've downloaded/loaded in the client so other people can find yours in the search.

The UI is a bit difficult to understand, takes a while to figure it out how to actually use it IMO. Probably a good idea to read the usage manual on their github page.

I've been using SystemRescue (formerly SystemRescueCD) since forever & it's usually more than enough for anything I need to get done. Though nowadays just about any Linux live image can probably do the job if that's all you have at the moment.

The issue seems to stem from the fact that the blocked communities posted direct links to copyrighted content

Incorrect, !piracy@lemmy.dbzer0.com has a rule forbidding direct links to content. If those posts/comments exist mods there would simply remove them for breaking rules. Sort of seems like you're making random assumptions.

Most rational people choose to limit their exposure to liability before it happens

I had a feeling someone was going to reply with the "let's ban things because they might be problematic in the future" reasoning. What's interesting with your line of thinking is that there are many more communities that Lemmy.world admins should also consider banning due to possibly being a legal issue later on. In fact Lemmy.world admins haven't even banned all piracy related/adjacent communities, they literally only considered the select few that were mentioned by the troll account.

I'd argue with this action Lemmy.world admins have actually put themselves in a more legally dubious position. They are now picking and choosing which sorts of liability to be exposed to. There is now historical precedence that the Lemmy.world admins specifically choose what to keep unblocked on their instance.

Sounds like you're assuming there was some legal issue that triggered this community blocking? Lemmy.world admins did not receive any legal notices prior to this action, it was just their kneejerk response to a troll from another instance. You can view it yourself, browse to the post via !support@lemmy.world or see it directly https://lemmy.world/post/3175920

There were no legal issues or threats, it was just some troll with a brand new account from a different instance that tricked admins into blocking those communities. See the other post https://lemmy.world/post/3175920 (if it loads, lemmy.world having uptime issues as usual)

You can browse to it via !support@lemmy.world or see the post directly https://lemmy.world/post/3175920

EDIT: Lemmy.world seems to be down right this second so you may not be able to load it, LOL.

Piracy subreddits still exist on Reddit. Lemmy.world admins are apparently blocking communities that even Reddit allows.

We already do :) It's all federated so dbzer0 members can view/subscribe/participate in other Lemmy communities.

Banning piracy? Like the mere encouragement or?

Just the mere encouragement & discussion, yes. The banned communities do not allow direct links to pirated content (!piracy@lemmy.dbzer0.com has a rule forbidding that).

It's strange to see people saying there was some sort of legit reasoning, the lemmy.world admins did not receive any sort of legal DMCA/NTD request or anything of the sort. They were simply trolled hard by a brand new account from lemm.ee asking to defederate from "piracy" communities and lemmy.world admins took the bait. See the post yourself https://lemmy.world/post/3175920

Incidentally that same user has created troll accounts at other instances & have been getting themselves banned, they were already banned at the dbzer0 instance (see https://lemmy.dbzer0.com/comment/1956277) so it looks like it was simple retaliation to attempt to trick other instances into defederating/blocking them.