Hi Harald, service gsad restart did the trick, thanks a lot!
Have a nice weekend, Johannes On 16 Feb 2014, at 12:00, [email protected] wrote: > Send Openvas-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Openvas-discuss digest..." > > > Today's Topics: > > 1. GSAD not listening on correct interface (Johannes Schoenborn) > 2. Re: GSAD not listening on correct interface (Reindl Harald) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 16 Feb 2014 10:43:32 +0100 > From: Johannes Schoenborn <[email protected]> > To: [email protected] > Subject: [Openvas-discuss] GSAD not listening on correct interface > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252 > > Hi there, > > I can?t connect to my running GSAD, as it looks like the service is not > listening on the wireless interface of the VM. > > I?ve got a CentOS connected through a physically attached USB WLAN stick. > My host machine can ping the VM and vice versa. If I try to connect to i.e. > port 9392, the browser of the host machine will tell me ?not reachable?. > > GSAD is running locally, a curl on the GSAD port displays the forward to the > login page - on the OpenVAS VM itself. > > I tried to adjust the ?listen argument from 127.0.0.1 to i.e. 192.168.1.10, > which is the IP address of the wireless stick. No success. > > Any ideas? > > I?d start GSAD i.e. via gsad -p 9392 -http-only -v -listen=192.168.1.10 > ?foreground > > Gsad.log is full of happiness, no errors here. > > I?d assume Its either GSAD not correctly listening on the wireless device or > a setup problem with the wireless device? > > Thanks in advance, > Johannes > > > > ------------------------------ > > Message: 2 > Date: Sun, 16 Feb 2014 11:29:08 +0100 > From: Reindl Harald <[email protected]> > To: [email protected] > Subject: Re: [Openvas-discuss] GSAD not listening on correct interface > Message-ID: <[email protected]> > Content-Type: text/plain; charset="windows-1252" > > > > Am 16.02.2014 10:43, schrieb Johannes Schoenborn: >> I can?t connect to my running GSAD, as it looks like the service is not >> listening on the wireless interface of the VM. >> I?ve got a CentOS connected through a physically attached USB WLAN stick > > does not matter > >> My host machine can ping the VM and vice versa. If I try to connect to i.e. >> port 9392, the browser of the host machine will tell me ?not reachable?. >> GSAD is running locally, a curl on the GSAD port displays the forward to the >> login page - on the OpenVAS VM itself. >> >> I tried to adjust the ?listen argument from 127.0.0.1 to i.e. 192.168.1.10, >> which is the IP address of the wireless stick. No success. > > where did you do that? > >> Any ideas? > > make the change in the correct confgig files > >> I?d start GSAD i.e. via gsad -p 9392 -http-only -v -listen=192.168.1.10 >> ?foreground > > I'd not because change the configuration would be more effective > and "service gsad start / stop / restart" is the way to go > > as you can see in the ps aux output below these parameters are > used for the commandline > > [root@openvas:~]$ cat /etc/sysconfig/gsad > GSA_ADDRESS=0.0.0.0 > GSA_PORT=443 > GSA_SSL_PRIVATE_KEY=/var/lib/openvas/CA/openvas.thelounge.net.pem > GSA_SSL_CERTIFICATE=/var/lib/openvas/CA/openvas.thelounge.net.pem > GSA_SSL_CIPHERS=TLS_DHE_RSA_AES_256_CBC_SHA1 > ADMINISTRATOR_ADDRESS=127.0.0.1 > ADMINISTRATOR_PORT=9393 > MANAGER_ADDRESS=127.0.0.1 > MANAGER_PORT=9390 > >> Gsad.log is full of happiness, no errors here. > > because there is no error > >> I?d assume Its either GSAD not correctly listening on the wireless device or >> a setup problem with the wireless device? > > why the hell do you assume instead confirm and provide basic informations > > [root@openvas:~]$ netstat --numeric-hosts --numeric-ports --notrim --programs > -u -t > Aktive Internetverbindungen (Nur Server) > Proto Recv-Q Send-Q Local Address Foreign Address > State PID/Program name > tcp 0 0 127.0.0.1:9390 0.0.0.0:* > LISTEN 4408/openvasmd > tcp 0 0 127.0.0.1:9391 0.0.0.0:* > LISTEN 7529/openvassd > tcp 0 0 127.0.0.1:9393 0.0.0.0:* > LISTEN 1189/openvasad > tcp 0 0 0.0.0.0:443 0.0.0.0:* > LISTEN 1210/gsad > tcp 0 0 0.0.0.0:10022 0.0.0.0:* > LISTEN 1201/sshd > > [root@openvas:~]$ ps aux | grep gsad > root 1210 0.0 0.0 120224 2076 ? Sl Feb12 0:00 > /usr/sbin/gsad --listen=0.0.0.0 --port=443 > --ssl-private-key=/var/lib/openvas/CA/openvas.thelounge.net.pem > --ssl-certificate=/var/lib/openvas/CA/openvas.thelounge.net.pem > --alisten=127.0.0.1 --aport=9393 > --mlisten=127.0.0.1 --mport=9390 > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 246 bytes > Desc: OpenPGP digital signature > URL: > <http://lists.wald.intevation.org/pipermail/openvas-discuss/attachments/20140216/5d216e59/attachment-0001.sig> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > ------------------------------ > > End of Openvas-discuss Digest, Vol 85, Issue 9 > ********************************************** _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
