You can try to set RSYNC_PROXY env. variable, may be with the http_proxy
value of your machine.
On Wed, Sep 16, 2015 at 22:20 Eero Volotinen <[email protected]> wrote:

> Hi,
>
> Well, looks like there is no other support at this moment. How about
> opening firewall for rsync?
>
> or else you need to create workaround on other server and then download
> data using wget?
>
> --
> Eero
>
> 2015-09-17 8:14 GMT+03:00 xie <[email protected]>:
>
>> Hi team,
>>
>> When I install Openvas tool, I cannot have an access to feed.openvas.org
>> with rsync and download scap data or nvt data in my lab. So The updating
>> procedure has always failed with the below erro. Is there any way around
>> for the command, openvas-scapdata-sync.  I can see the option, -wget is not
>> supported any more while the command, openvas-nvt-sync can still support
>> the option.
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++
>>
>> [root@CentOS654354911 ~]# openvas-scapdata-sync
>> [i] This script synchronizes a SCAP data directory with the OpenVAS one.
>> [i] SCAP dir: /var/lib/openvas/scap-data
>> [i] Will use rsync
>> [i] Using rsync: /usr/bin/rsync
>> [i] Configured SCAP data rsync feed: rsync://feed.openvas.org:/scap-data
>> rsync: failed to connect to feed.openvas.org: Connection timed out (110)
>> rsync error: error in socket IO (code 10) at clientserver.c(124)
>> [receiver=3.0.6]
>> [e] Error: rsync failed. Your SCAP data might be broken now.
>>
>> +++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>> Thanks
>> Neo Xie
>>
>> _______________________________________________
>> Openvas-discuss mailing list
>> [email protected]
>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>>
>
> _______________________________________________
> Openvas-discuss mailing list
> [email protected]
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to