Only seems to attack 3 IPs about db1000n

[arriven]

@alextatarinov @arthur2406 @bunge12 you're using a mode that only shows important logs, the IP there is from one of the experimental jobs that doesn't respect that (and there's already a bit more effective job with the same functionality, we just didn't get to reconfiguring that target yet). If you want to see all the info - add -l 0 to the commandline arguments to enable debug logging (but be careful, there's a lot of it)
@WeGoToMars since you were using debug logs already, can you check it out with the latest version and provide a full log of an app running for at least a minute?

[WeGoToMars]

@arriven -c https://blah completely fixed the issue for me, it now works on multiple IPs and shows logs correctly. Thanks!

[alextatarinov]

Similar issue - targets only one IP

[arthur2406]

Similar issue - targets only one IP

The same issue

[bunge12]

My output looks different, but I can also see only one IP (178.248.236.218)

[WeGoToMars]

@arriven downloaded latest build for amd64, running on win11
here is a piece of the log I'm seeing https://pastebin.com/raKTKG8n, it's not a full minute because pastebin has limit for free users, but it really stays the same.

On a side note, there seems to be some kind of an error with calculating the speed, it seems to drift upwards but network activity in task manager never changes (~2.5 mbps up/~4.5 mbps down).

[su-hs]

My results:

docker run --rm -it ghcr.io/arriven/db1000n:latest

[arriven]

@WeGoToMars the log you provided this time also doesn't seem to include debug logs :)
The main reason network usage drifts up and down here is that the job outputting it's IP doesn't contribute to the overall metrics (it's simply an integrated module and will be replaced by other, more effective job). You can try out the backup config embedded into the app (it uses latest features) in the latest release by providing an invalid url for the main config (for example run it with -c https://blah). Coordinators will soon update the default remote config to use latest features but it's already effective as is

[arriven]

@WeGoToMars cool, but please check https://github.com/db1000n-coordinators/LoadTestConfig and remove that commandline argument as soon as activity starts there to keep being up to date with current targets (I've almost finished instructing admins on how to manage it so it should become active very soon)

[WeGoToMars]

@arriven db1000n.exe -c https://github.com/db1000n-coordinators/LoadTestConfig/blob/main/config.json seems to work now

Without any arguments, the logging works differently(?)

db1000n.exe -c https://github.com/db1000n-coordinators/LoadTestConfig/blob/main/config.json:
[INFO] Attacking https://lenta.ru/
[INFO] Attacking https://lenta.ru/login
...

db1000n.exe:
[INFO] Атака проводиться успішно! Руський воєнний корабль іди нахуй!
[INFO] The app is generating approximately 34394 bytes per second
It prints this stat every minute, and it would be great if it could be more frequent (once every 1-10s)

db1000n.exe -l 0 shows attacks on all 6 targets outlined in the LoadTestConfig/main/config.json