-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit number of outgoing connections #348
Comments
This may be a good solution |
Any other options instead of reducing dht_crawler.scaling_factor ? I tried setting it to
Just tried setting the value to Saw that VPN might be possible fix but that doesn't seem like great solution.. |
Ok this seems to work in docker compose: services:
bitmagnet:
image: ghcr.io/bitmagnet-io/bitmagnet:latest
ulimits:
nofile:
soft: 1024
hard: 2048
container_name: bitmagnet
ports:
# API and WebUI port:
- "3333:3333"
# BitTorrent ports:
- "3334:3334/tcp"
- "3334:3334/udp"
restart: unless-stopped
environment:
- POSTGRES_HOST=postgres
- POSTGRES_PASSWORD=XXXXXXXXXXX
- DHT_CRAWLER_SCALING_FACTOR=2
... By setting low
Also reduced |
Are those documented somewhere? |
Documented where? BitMagnet, Docker, or Linux ? For Docker and Linux use google/search for general info. |
See
on your system for technical documentation about the Linux basics. Compose Reference for docker-compose specific stuff. It's a service level element. Just search for ulimits here. |
It works, partly. I set those to 512-1024 and also a rule at router firewall to drop any outgoing UDP connections from bitmagnet exceeding 1024. Got 170k dropped connections in 9 hours. Still better than before, but hardly a solution. |
I have ended up with following values:
My network seems stable, no more disconnects and other issues. Edit: |
Is your feature request related to a problem? Please describe
When active and crawling BM opened thousands of outgoing UDP connections triggering ISP limit and making internet access for other clients unreachable.
Describe the solution you'd like
Add a setting to limit a number of active outgoing connections.
The text was updated successfully, but these errors were encountered: