Re: [Openvas-discuss] openvas manager not listening and scan results are blank

[William Coquelin]

Mark, look here:

WARNING: OpenVAS Manager is running and listening only on the local 
interface.
This means that you will not be able to access the OpenVAS Manager from 
the
outside using GSD or OpenVAS CLI.
SUGGEST: Ensure that OpenVAS Manager listens on all interfaces unless 
you want
a local service only.

Looks like maybe your VM isn’t using the Ethernet connector or it may be 
defaulted off.  Enable that and rerun the test.

Bill




From: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] On 
Behalf Of Eero Volotinen
Sent: Wednesday, August 10, 2016 3:47 PM
To: Mark Pleis <mpl...@mcfarlandclinic.com>
Cc: openvas-discuss@wald.intevation.org
Subject: Re: [Openvas-discuss] openvas manager not listening and scan results 
are blank


Just read the comments from file.

Eeeo

10.8.2016 9.50 ip. "Mark Pleis" 
<mpl...@mcfarlandclinic.com<mailto:mpl...@mcfarlandclinic.com>> kirjoitti:
I am new to the world of OpenVAS and I am having two issues getting it up and 
running. I have been googling for the past 3 days and documentation seems to be 
sparse. I am asking these together because I fel they could be related some how.

1. I can't get the manager to work on all interfaces, I have changed the config 
setting in the
/etc/default folder for the services and no luck I have restarted the services 
and the VM.
2.  I am not able to scan.  when I setup a scan on the local console for an out 
side machine or the local hst i get no results.
I tried using nmap on this machine and it did work

Details
---
Kali Linux  rolling image running on VMware 5.5
OpenVAS ver 8
only 1 NIC eth0 and of cource lo
I have add below all the config files and the openvas-check-setup results.  I 
know this has to be simple and I am missing
something, but I just can't find it.

Thanks in advance.
Mark


config files below
--





---
# cat openvas-manager
---
# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the openvas-manager.service file. If you want to change
# them you should override the service file by creating a file
# /etc/systemd/system/openvas-manager.service.d/local.conf like this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/openvasmd 

# The file the OpenVAS Manager will use as database.
DATABASE_FILE=/var/lib/openvas/mgr/tasks.db

# The address the OpenVAS Manager will listen on.
MANAGER_ADDRESS=0.0.0.0

# The port the OpenVAS Manager will listen on.
MANAGER_PORT=9390


--
# cat openvas-scanner
--
# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the openvas-scanner.service file. If you want to change
# them you should override the service file by creating a file
# /etc/systemd/system/openvas-scanner.service.d/local.conf like this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/openvassd 

# The address the OpenVAS Scanner is listening on.
SCANNER_ADDRESS=0.0.0.0

# The port the OpenVAS Scanner is listening on.
SCANNER_PORT=9391
---
# cat greenbone-security-assistant

# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the greenbone-security-assistant.service file. If you want to 
change
# them you should override the service file by creating a file
# /etc/systemd/system/greenbone-security-assistant.service.d/local.conf like 
this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/gsad --foreground 

# The address the Greenbone Security Assistant will listen on.
GSA_ADDRESS=0.0.0.0

# The port the Greenbone Security Assistant will listen on.
GSA_PORT=9392

# The file to use as private key for HTTPS
#GSA_SSL_PRIVATE_KEY=

# The file to use as certificate for HTTPS
#GSA_SSL_CERTIFICATE=

# Should HTTP get redirected to HTTPS
# If $GSA_REDIRECT_PORT is not set it will redirect port 80.
#GSA_REDIRECT=1

# Redirect HTTP from this port to $GSA_PORT
# For this being effective $GSA_REDIRECT has to be set to 1.
#GSA_REDIRECT_PORT=9394

# The address the OpenVAS Manager is listening on.
MANAGER_ADDRESS=127.0.0.1

# The port the OpenVAS Manager is listening on.
MANAGER_PORT=9390


---
# openvas-check-setup
---

openvas-check-setup 2.3.3
  Test completeness and readiness of Open

Re: [Openvas-discuss] openvas manager not listening and scan results are blank

[Mark Pleis]

The VMware interface is up and I am able the ping out and  get to the Kali
repository..

Item 2 appears to be resolved


On Wed, Aug 10, 2016 at 3:02 PM, William Coquelin <wcoque...@emigra.com>
wrote:

> Mark, look here:
>
>
>
> WARNING: OpenVAS Manager is running and listening only on the
> local interface.
>
> This means that you will not be able to access the OpenVAS Manager
> from the
>
> outside using GSD or OpenVAS CLI.
>
> SUGGEST: Ensure that OpenVAS Manager listens on all interfaces
> unless you want
>
> a local service only.
>
>
>
> Looks like maybe your VM isn’t using the Ethernet connector or it may be
> defaulted off.  Enable that and rerun the test.
>
>
>
> Bill
>
>
>
>
>
>
>
>
>
> *From:* Openvas-discuss [mailto:openvas-discuss-
> boun...@wald.intevation.org] *On Behalf Of *Eero Volotinen
> *Sent:* Wednesday, August 10, 2016 3:47 PM
> *To:* Mark Pleis <mpl...@mcfarlandclinic.com>
> *Cc:* openvas-discuss@wald.intevation.org
> *Subject:* Re: [Openvas-discuss] openvas manager not listening and scan
> results are blank
>
>
>
> Just read the comments from file.
>
> Eeeo
>
>
>
> 10.8.2016 9.50 ip. "Mark Pleis" <mpl...@mcfarlandclinic.com> kirjoitti:
>
> I am new to the world of OpenVAS and I am having two issues getting it up
> and running. I have been googling for the past 3 days and documentation
> seems to be sparse. I am asking these together because I fel they could be
> related some how.
>
>
>
> 1. I can't get the manager to work on all interfaces, I have changed the
> config setting in the
>
> /etc/default folder for the services and no luck I have restarted the
> services and the VM.
>
> 2.  I am not able to scan.  when I setup a scan on the local console for
> an out side machine or the local hst i get no results.
>
> I tried using nmap on this machine and it did work
>
>
>
> Details
>
> ---
>
> Kali Linux  rolling image running on VMware 5.5
>
> OpenVAS ver 8
>
> only 1 NIC eth0 and of cource lo
>
> I have add below all the config files and the openvas-check-setup
> results.  I know this has to be simple and I am missing
>
> something, but I just can't find it.
>
>
>
> Thanks in advance.
>
> Mark
>
>
>
> 
>
> config files below
>
> --
>
>
>
>
>
>
>
>
>
>
>
> 
> ---
>
> # cat openvas-manager
>
> 
> ---
>
> # NOTE: This file is not used if you are using systemd. The options are
>
> # hardcoded in the openvas-manager.service file. If you want to change
>
> # them you should override the service file by creating a file
>
> # /etc/systemd/system/openvas-manager.service.d/local.conf like this:
>
> # [Service]
>
> # ExecStart=
>
> # ExecStart=/usr/sbin/openvasmd 
>
>
>
> # The file the OpenVAS Manager will use as database.
>
> DATABASE_FILE=/var/lib/openvas/mgr/tasks.db
>
>
>
> # The address the OpenVAS Manager will listen on.
>
> MANAGER_ADDRESS=0.0.0.0
>
>
>
> # The port the OpenVAS Manager will listen on.
>
> MANAGER_PORT=9390
>
>
>
>
>
> 
> --
>
> # cat openvas-scanner
>
> 
> --
>
> # NOTE: This file is not used if you are using systemd. The options are
>
> # hardcoded in the openvas-scanner.service file. If you want to change
>
> # them you should override the service file by creating a file
>
> # /etc/systemd/system/openvas-scanner.service.d/local.conf like this:
>
> # [Service]
>
> # ExecStart=
>
> # ExecStart=/usr/sbin/openvassd 
>
>
>
> # The address the OpenVAS Scanner is listening on.
>
> SCANNER_ADDRESS=0.0.0.0
>
>
>
> # The port the OpenVAS Scanner is listening on.
>
> SCANNER_PORT=9391
>
> 
> ---
>
> # cat greenbone-security-assistant
>
> 
> 
>
> # NOTE: This file is not used if you are using systemd. The options are
>
> # hardcoded in the greenbone-security-assistant.service file. If you want
> to change
>
> # them you s

Re: [Openvas-discuss] openvas manager not listening and scan results are blank

[Eero Volotinen]

Just read the comments from file.

Eeeo

10.8.2016 9.50 ip. "Mark Pleis"  kirjoitti:

> I am new to the world of OpenVAS and I am having two issues getting it up
> and running. I have been googling for the past 3 days and documentation
> seems to be sparse. I am asking these together because I fel they could be
> related some how.
>
> 1. I can't get the manager to work on all interfaces, I have changed the
> config setting in the
> /etc/default folder for the services and no luck I have restarted the
> services and the VM.
> 2.  I am not able to scan.  when I setup a scan on the local console for
> an out side machine or the local hst i get no results.
> I tried using nmap on this machine and it did work
>
> Details
> ---
> Kali Linux  rolling image running on VMware 5.5
> OpenVAS ver 8
> only 1 NIC eth0 and of cource lo
> I have add below all the config files and the openvas-check-setup
> results.  I know this has to be simple and I am missing
> something, but I just can't find it.
>
> Thanks in advance.
> Mark
>
> 
> config files below
> --
>
>
>
>
>
> 
> ---
> # cat openvas-manager
> 
> ---
> # NOTE: This file is not used if you are using systemd. The options are
> # hardcoded in the openvas-manager.service file. If you want to change
> # them you should override the service file by creating a file
> # /etc/systemd/system/openvas-manager.service.d/local.conf like this:
> # [Service]
> # ExecStart=
> # ExecStart=/usr/sbin/openvasmd 
>
> # The file the OpenVAS Manager will use as database.
> DATABASE_FILE=/var/lib/openvas/mgr/tasks.db
>
> # The address the OpenVAS Manager will listen on.
> MANAGER_ADDRESS=0.0.0.0
>
> # The port the OpenVAS Manager will listen on.
> MANAGER_PORT=9390
>
>
> 
> --
> # cat openvas-scanner
> 
> --
> # NOTE: This file is not used if you are using systemd. The options are
> # hardcoded in the openvas-scanner.service file. If you want to change
> # them you should override the service file by creating a file
> # /etc/systemd/system/openvas-scanner.service.d/local.conf like this:
> # [Service]
> # ExecStart=
> # ExecStart=/usr/sbin/openvassd 
>
> # The address the OpenVAS Scanner is listening on.
> SCANNER_ADDRESS=0.0.0.0
>
> # The port the OpenVAS Scanner is listening on.
> SCANNER_PORT=9391
> 
> ---
> # cat greenbone-security-assistant
> 
> 
> # NOTE: This file is not used if you are using systemd. The options are
> # hardcoded in the greenbone-security-assistant.service file. If you want
> to change
> # them you should override the service file by creating a file
> # /etc/systemd/system/greenbone-security-assistant.service.d/local.conf
> like this:
> # [Service]
> # ExecStart=
> # ExecStart=/usr/sbin/gsad --foreground 
>
> # The address the Greenbone Security Assistant will listen on.
> GSA_ADDRESS=0.0.0.0
>
> # The port the Greenbone Security Assistant will listen on.
> GSA_PORT=9392
>
> # The file to use as private key for HTTPS
> #GSA_SSL_PRIVATE_KEY=
>
> # The file to use as certificate for HTTPS
> #GSA_SSL_CERTIFICATE=
>
> # Should HTTP get redirected to HTTPS
> # If $GSA_REDIRECT_PORT is not set it will redirect port 80.
> #GSA_REDIRECT=1
>
> # Redirect HTTP from this port to $GSA_PORT
> # For this being effective $GSA_REDIRECT has to be set to 1.
> #GSA_REDIRECT_PORT=9394
>
> # The address the OpenVAS Manager is listening on.
> MANAGER_ADDRESS=127.0.0.1
>
> # The port the OpenVAS Manager is listening on.
> MANAGER_PORT=9390
>
>
> 
> ---
> # openvas-check-setup
> 
> ---
>
> openvas-check-setup 2.3.3
>   Test completeness and readiness of OpenVAS-8
>   (add '--v6' or '--v7' or '--v9'
>if you want to check for another OpenVAS version)
>
>   Please report us any non-detected problems and
>   help us to improve this check routine:
>   http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
>
>   Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the
> problem.
>
>   Use the parameter --server to skip checks for client tools
>   like GSD and OpenVAS-CLI.
>
> Step 1: Checking OpenVAS Scanner ...
> OK: OpenVAS Scanner is present in version 5.0.5.
> OK: OpenVAS Scanner CA Certificate is present as
> /var/lib/openvas/CA/cacert.pem.
> OK: 

Re: [Openvas-discuss] openvas manager not listening and scan results are blank

[Chris]

Hi,

> 1. I can't get the manager to work on all interfaces, I have changed
the config setting in the  /etc/default folder for the services and no
luck I have restarted the services and the VM.

have a look at the notice of the attached config settings:

> # NOTE: This file is not used if you are using systemd.

Kali Linux is probably already on systemd. If you need further
configuration help its probably also recommended to ask at the Kali
forums for help as they know their system a little bit better then most
of the users at this list.

> 2.  I am not able to scan.  when I setup a scan on the local console
for an out side machine or the local hst i get no results.

Unfurtunately this contains too few info to be able to help here. A
starting point would be info like:

- Which scan config have you used?
- Are yo getting absolutely no results or only a few log lines?
- Are the systems you're trying to scan reachable via an ICMP Ping?
(Note the "Alive Test" config when creating a new target:
http://docs.greenbone.net/GSM-Manual/gos-3.1/en/scanning.html#creating-a-target)
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

[Openvas-discuss] openvas manager not listening and scan results are blank

[Mark Pleis]

I am new to the world of OpenVAS and I am having two issues getting it up
and running. I have been googling for the past 3 days and documentation
seems to be sparse. I am asking these together because I fel they could be
related some how.

1. I can't get the manager to work on all interfaces, I have changed the
config setting in the
/etc/default folder for the services and no luck I have restarted the
services and the VM.
2.  I am not able to scan.  when I setup a scan on the local console for an
out side machine or the local hst i get no results.
I tried using nmap on this machine and it did work

Details
---
Kali Linux  rolling image running on VMware 5.5
OpenVAS ver 8
only 1 NIC eth0 and of cource lo
I have add below all the config files and the openvas-check-setup results.
I know this has to be simple and I am missing
something, but I just can't find it.

Thanks in advance.
Mark


config files below
--





---
# cat openvas-manager
---
# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the openvas-manager.service file. If you want to change
# them you should override the service file by creating a file
# /etc/systemd/system/openvas-manager.service.d/local.conf like this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/openvasmd 

# The file the OpenVAS Manager will use as database.
DATABASE_FILE=/var/lib/openvas/mgr/tasks.db

# The address the OpenVAS Manager will listen on.
MANAGER_ADDRESS=0.0.0.0

# The port the OpenVAS Manager will listen on.
MANAGER_PORT=9390


--
# cat openvas-scanner
--
# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the openvas-scanner.service file. If you want to change
# them you should override the service file by creating a file
# /etc/systemd/system/openvas-scanner.service.d/local.conf like this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/openvassd 

# The address the OpenVAS Scanner is listening on.
SCANNER_ADDRESS=0.0.0.0

# The port the OpenVAS Scanner is listening on.
SCANNER_PORT=9391
---
# cat greenbone-security-assistant

# NOTE: This file is not used if you are using systemd. The options are
# hardcoded in the greenbone-security-assistant.service file. If you want
to change
# them you should override the service file by creating a file
# /etc/systemd/system/greenbone-security-assistant.service.d/local.conf
like this:
# [Service]
# ExecStart=
# ExecStart=/usr/sbin/gsad --foreground 

# The address the Greenbone Security Assistant will listen on.
GSA_ADDRESS=0.0.0.0

# The port the Greenbone Security Assistant will listen on.
GSA_PORT=9392

# The file to use as private key for HTTPS
#GSA_SSL_PRIVATE_KEY=

# The file to use as certificate for HTTPS
#GSA_SSL_CERTIFICATE=

# Should HTTP get redirected to HTTPS
# If $GSA_REDIRECT_PORT is not set it will redirect port 80.
#GSA_REDIRECT=1

# Redirect HTTP from this port to $GSA_PORT
# For this being effective $GSA_REDIRECT has to be set to 1.
#GSA_REDIRECT_PORT=9394

# The address the OpenVAS Manager is listening on.
MANAGER_ADDRESS=127.0.0.1

# The port the OpenVAS Manager is listening on.
MANAGER_PORT=9390


---
# openvas-check-setup
---

openvas-check-setup 2.3.3
  Test completeness and readiness of OpenVAS-8
  (add '--v6' or '--v7' or '--v9'
   if you want to check for another OpenVAS version)

  Please report us any non-detected problems and
  help us to improve this check routine:
  http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

  Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the
problem.

  Use the parameter --server to skip checks for client tools
  like GSD and OpenVAS-CLI.

Step 1: Checking OpenVAS Scanner ...
OK: OpenVAS Scanner is present in version 5.0.5.
OK: OpenVAS Scanner CA Certificate is present as
/var/lib/openvas/CA/cacert.pem.
OK: OpenVAS Scanner server certificate is valid and present as
/var/lib/openvas/CA/servercert.pem.
OK: redis-server is present in version v=3.2.3.
OK: scanner (kb_location setting) is configured properly using the
redis-server socket: /var/lib/redis/redis.sock
OK: redis-server is running and listening on socket:
/var/lib/redis/redis.sock.
OK: