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
I run into problem with rqbit, when running it as service/daemon on Linux - after about 2 days of running it I saw that there 20k connections in WAIT-CLOSE state and also a lot of connections in FIN_WAIT state. It actually brought down TCP on linux machine to pathetic performance - tens of KB/s.
My "theory" is that rqbit is accepting connections without any limitation - after while a lot of peers is trying to connect as we are visible in DHT. It's then kind of DoS TCP attack - and that was actually how I solved it - set up DoS protection on my router/fw - which rate limits number of new TCP connections.
Just wondering if something can be done in rqbit direcly - limit a rate of new incoming TCP connections.
The text was updated successfully, but these errors were encountered:
The only limit that exists right now afaik is 128 (hard coded) outgoing connections per torrent. Definitely introducing more limits, including the number of accepted connections makes sense
I run into problem with rqbit, when running it as service/daemon on Linux - after about 2 days of running it I saw that there 20k connections in WAIT-CLOSE state and also a lot of connections in FIN_WAIT state. It actually brought down TCP on linux machine to pathetic performance - tens of KB/s.
My "theory" is that rqbit is accepting connections without any limitation - after while a lot of peers is trying to connect as we are visible in DHT. It's then kind of DoS TCP attack - and that was actually how I solved it - set up DoS protection on my router/fw - which rate limits number of new TCP connections.
Just wondering if something can be done in rqbit direcly - limit a rate of new incoming TCP connections.
The text was updated successfully, but these errors were encountered: