Increment number of max-connection-per-server

[lardissone]

Is there a way to increment this max to something higher than 16?

Why is this limitation?

[tatsuhiro-t]

16 is plenty. Too easy to do DOS.
If you want more, change the source code as you like.

[Saren-Arterius]

16 is plenty. Too easy to do DOS.
If you want more, change the source code as you like.

1. Aria2 is not a great tool for DoS.
2. If Aria2 is will be used for a tool for DoS, the attacker could change to a higher value and re-compile it. So why bother limit it in source code?
3. Server host could easily block the offending connections.
4. If we need it, we know what we are doing.

Therefore, the 16 limit is not necessary. Please re-consider.

[recolic]

Azure official tool azcopy creates 128 connections by default, and has 1300Mbps download speed in MSFT intranet.
But aria2c has only 70 Mbps download speed. TCP window size limit in a high latency connection restricts bandwidth of single connection.

aria2c is "the ultra fast download utility", but it's not.

---

btw, it's still too easy to do DOS in this way, please close the whole aria2 project.

while true
    nohup aria2c -x 1 http://some.naive.target.com/naive.target & disown
end

[expecttheunusual]

Besides, hackers could provide a malicious version of aria2c which has no 16-limit. Sure, you are protecting the servers, but doing so will indirectly put your clients at risk because you don't actually give the users what they want. It's like getting a porsche with an engine of a fucking tractor. It's usable for normal users but for those that want more out of it, naturally get pretty annoyed at the limits. The normal users that do not have mechanic-skills can't use the porsche as fast as they want to.