Hi everyone,
I am mostly performing scans on networks were bandwidth consumption is
critical and should therefore be as low as possible.
>From my first observations, the most bandwidth-intensive part of the scan
is the beginning, were lots of NMAP processes are being triggered, like so:
---openvas
Hi,
On 07.06.2018 15:06, Alexandre Brasseur wrote:
> I checked every parameters you mentioned and I confirm those are not set
> (empty string) in my current scan config:
this currently works as expected with the recent OpenVAS releases listed
at http://www.openvas.org/install-source.html.
When c
Hi Christian,
Thanks for your quick answer.
I checked every parameters you mentioned and I confirm those are not set
(empty string) in my current scan config:
* Nmap (NASL wrapper)
Do not randomize the order in which ports are scanned = "no"
Do not scan targets not in the file = "no"
Hi,
could you make sure that you havn't changed any of the following
settings of the "nmap.nasl" preferences from the default / empty string:
Max Retries :
Host Timeout (ms) :
Min RTT Timeout (ms) :
Max RTT Timeout (ms) :
Initial RTT Timeout (ms) :
Ports scanned in parallel (min)
Ports scanned in
Hi everyone,
I am mostly performing scans on networks were bandwidth consumption is
critical and should therefore be as low as possible.
>From my first observations, the most bandwidth-intensive part of the scan
is the beginning, were lots of NMAP processes are being triggered, like so:
---openva
