Certain peers result in it essentially stalling. #3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I noticed certain peers would cause it to stop uploading. Pausing and resuming would allow uploading again until the peer shows up again. I tried blocking the peer via iptables, but it doesn't seem to work for me.
Docker is a pain in the ass.
Interesting. I'm certain iptables should be capable of blocking them, perhaps you configured it wrong. There is also a plugin for Deluge that allows blocking of IPs https://dev.deluge-torrent.org/wiki/Plugins/Blocklist ... I may have to look into some heuristics for detecting peers that aren't going to download or download too slowly.
As for Docker, you don't have to use it. You can run build.sh outside of the container (at your own risk, you may have to modify paths in the script)
Yes, that could be the case.
I will try this.
This would be even better as it would require less manual intervention.
Yeah, I'm going to try it out this way too.
I had the same problem, for me blocking through iptables with docker worked that way: iptables -I FORWARD -i docker0 -d $IP -j DROP
I think it would be a good enough compromise to serve the next piece even though not all peers have it, as soon as the majority has it.
Also it seems to be very slow when premiere is enabled and there is only one peer.
Glad it worked for you. Pretty odd that you're both experiencing problems like that.
This seems less nuanced than individually pruning bad peers, and will make your ratio suffer more for it.
I suppose that makes sense... auto-snatchers do really weird things and some of them still end up managing to get 2.0 ratio even with premiere, I have no idea how.
Right, so Andys command doesn't work for me and it's always the same peer. Is it because of --network host switch? I can't seem to block it no matter what I try. I have to keep pausing and resuming the torrent to get it to complete.
--
By the way, I tried to get it working outside of docker. It wasn't easy and in the end I couldn't get it to work.
Would be really neat if you could use normal deluge and just use the plugin itself for the functionality. I don't know if that's feasible or not.
--
Additionally, I have much better results when setting the piece size to a high value. 16mb is working well for me. Only problem is this troublesome peer.
EDIT: OK. I managed to block him, I think. Assuming he was on this torrent.
iptables -A INPUT -s ip.address.here -j DROP
I'm currently working on a version that won't be a plug-in nor a modification to libtorrent. It will be a stand-alone script that you run alongside vanilla Deluge.
Hi, are you still working on this? I would love a stand-alone script.