epi052 / feroxbuster

A fast, simple, recursive content discovery tool written in Rust.
https://epi052.github.io/feroxbuster/
MIT License
5.56k stars 470 forks source link

[BUG] Internet slow down after using feroxbuster #1124

Closed BrunoTeixeira1996 closed 3 weeks ago

BrunoTeixeira1996 commented 2 months ago

Describe the bug For some reason when I use feroxbuster with 10 threads or less my internet connection slows down up until the point I need to reboot the router

To Reproduce Steps to reproduce the behavior:

  1. Start feroxbuster with 10 threads
  2. Watch internet slow down
  3. Check that its no longer possible to open internet pages
  4. Reboot router and stop feroxbuster

Expected behavior Its expected to not break the internet even by using a small amount of threads

Environment (please complete the following information):

epi052 commented 2 months ago

This sounds like an issue with your router, no? Or are you saying that a higher number of threads doesn't cause this behavior?

BrunoTeixeira1996 commented 2 months ago

This sounds like an issue with your router, no? Or are you saying that a higher number of threads doesn't cause this behavior?

A problem with my router? hmmm i've had the exact same issue using a different router in a different computer.

When using a small ammount of threads or a high ammount of threads feroxbuster crashes the network.

epi052 commented 1 month ago

so, when you experience this behavior, are there a bunch of directories all being scanned at the same time? Each directory is effectively its own scan, with its own threads, limits, etc...

you can use --scan-limit 1 to limit the scan to a single directory at a time. Further, you can limit the rate of requests per second with --rate-limit 100

further rate limiting documentation further scan limiting documentation

epi052 commented 3 weeks ago

closing this for now (housekeeping). feel free to reopen it to continue the conversation!

BrunoTeixeira1996 commented 3 weeks ago

@epi052 you can close this, looks like its already fixed!