You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few days ago, I noticed that some torrents had connections from an aria2 client with IP addresses in the range 116.132.0.0/16. At first, I didn't pay much attention to it, but later I noticed multiple several aria2 clients from the same IP range. Upon checking my blocklist history, I found that there were quite a few IP addresses marked as offline downloader from the 116.132.0.0/16.Do you want to add shielding from CN aria2/1.34.0?
Nowadays those leechers' names are changing quite frequently, so I think try to get rid of them only according to their peer-agents and peer-ids isn't reliable. Maybe we can try this project: https://github.com/PBH-BTN
I think those ips mentioned above are already in the banlist given by the BTN network.
Suggestion
A few days ago, I noticed that some torrents had connections from an aria2 client with IP addresses in the range 116.132.0.0/16. At first, I didn't pay much attention to it, but later I noticed multiple several aria2 clients from the same IP range. Upon checking my blocklist history, I found that there were quite a few IP addresses marked as offline downloader from the 116.132.0.0/16.Do you want to add shielding from CN aria2/1.34.0?
Use case
No response
Extra info/examples/attachments
#544
The text was updated successfully, but these errors were encountered: