A strange bug is causing the port scan results to be outrageous.

[Vulner-6]

1.If I use the --range command to limit the port range, I am still unable to discover open ports even when scanning at a very slow rate

2.If I use the -p command to specify the port, then I am able to discover open ports.

RustScan is a great tool with ambitious goals, but this scanning issue is indeed quite strange.

[bee-san]

Maybe --range is broken?

todo list:

• Try to recreate bug with --range
• Write a test for it

[PsypherPunk]

FWIW, I'm seeing the same results for --ports:

❯ ./target/release/rustscan --addresses 127.0.0.1 --ports 631 --greppable --scripts none 
127.0.0.1 -> [631]

…as I am with --range:

❯ ./target/release/rustscan --addresses 127.0.0.1 --range 600-650 --greppable --scripts none 
127.0.0.1 -> [631]

Most odd.

[PsypherPunk]

@Vulner-6, are you still seeing this?

And to check, based on your prompt, is this PowerShell on Windows?