*** Michael Meyer wrote:
> *** fschnit...@execulink.com wrote:
>
> > Ok, so as it appears _all_ of the OpenVAS default scanner configs use
> > a default scan mode of TCP Connect (connect()). I see that what I need
> > to do for my fast scans that are firewalled, is to
> > clone an existing
> >
*** fschnit...@execulink.com wrote:
> Ok, so as it appears _all_ of the OpenVAS default scanner configs use
> a default scan mode of TCP Connect (connect()). I see that what I need
> to do for my fast scans that are firewalled, is to
> clone an existing
> scan config, alter the clone, change the
*** fschnit...@execulink.com wrote:
>
> The only thing
> that works for me is to edit the nmap.nasl file and change:
> else
> argv[i++] = "-sT";
> to
> else argv[i++] = "-sS";
Edit the scanconfig. Edit family "Port scanners". Edit "Nmap (NASL
wrapper)". Change the "TCP scanning technique :" to
Ok, so as it appears _all_ of the OpenVAS default scanner configs use
a default scan mode of TCP Connect (connect()). I see that what I need
to do for my fast scans that are firewalled, is to
clone an existing
scan config, alter the clone, change the TCP Scanning Technique" to SYN
then use that
Hello,
Still tinkering with my ongoing slow scan issues. Basically
I'm on a Kali 2 box with OpenVAS 8, NMAP 7.31. When I'm port scanning
firewalls the scans take forever, 2 hours or more.
I've had some
recommendations to change firewall rules to REJECT instead of DROP. I've
done this and it has
Am 15.11.2016 um 23:54 schrieb Fábio Fernandes:
It has happened to me too. Analyzing further with tcpdump and strace i could
see that the retry speed rate seemed to be lower (maybe due to nmap adapting to
the conditions of the network like weak connection or firewalls) but the same
nmap
It has happened to me too. Analyzing further with tcpdump and strace i could
see that the retry speed rate seemed to be lower (maybe due to nmap adapting to
the conditions of the network like weak connection or firewalls) but the same
nmap command would finish in 15 to 20 minutes. I tried
Hi,
On 09.11.2016 22:48, fschnit...@execulink.com wrote:
> A good understanding
> of this behaviour would be great.
the nmap.nasl is just a "wrapper" of nmap and is calling plain nmap so
you might need to dig into nmap itself to see why it is sometimes faster
and the other time not.
Regards,
Hello,
I'm having trouble understanding why the same scan task/target
can take so long sometimes but not other times.
When I run a scan on
one host using the default OpenVAS port list and the Fast and Full scan
type, it can take as much as several hours or more to complete.
I can
see that the
