Wifi Router is down after running scan with "-a

[obreinx]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Architecture: [e.g. x86, x64, ARM ...]
  • OS: [e.g. Ubuntu, Kali, Arch ...]
  • Version [e.g. 20.04, Rolling, 8 ...]

Additional context Add any other context about the problem here.

[sidxparab]

hey @obreinx

• This issue generally arrives when you run reconFTW on your home network.
• As the steps like, dns bruteforcing use massdns as a base to generate a enormous amount of concurrent requets in a short span of time which indeed kills your wifi.
• Hence, if possible its recommended to run a scan on VPS

Fix:

• You can edit the reconftw.cfg config file which helps you to come over this situation.
• Set the value of the ```PUREDNS_PUBLIC_LIMIT ```` somewhere between 2000 to 10000 (depending on your preferences) https://github.com/six2dez/reconftw/blob/main/reconftw.cfg#L132

This will solve your issue for sure ✌

[xxxNamasteHxxx]

I just try to change PUREDNS_PUBLIC_LIMIT but the result is same while Running : Permutations Subdomain Enumeration ,my router still going down

[six2dez]

Then you should decrease even more that value, set something between 100 and 500 and then your router should be able to handle it. Otherwise this is not a reconftw issue but your hardware's limitation and reconftw has the option to adapt to your needs