Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scan /16 ranges #302

Closed
arkhelieldan opened this issue Oct 4, 2020 · 4 comments
Closed

Scan /16 ranges #302

arkhelieldan opened this issue Oct 4, 2020 · 4 comments
Labels
invalid This doesn't seem right

Comments

@arkhelieldan
Copy link

arkhelieldan commented Oct 4, 2020

I'm using the latest build, but I'm having problems with scanning in the cloud, I believe it's openvas' own, but it doesn't allow scheduling a scan or creating a list of targets with range / 16.

I have a VPC 10.10.0.0/16 and I need to scan new hosts that appear, since if I update the list with new IPs I will have to delete the schedule, the results and the current target.

Is there any way to scan with this range? I read that it is possible, but only if you make any changes to the GVMD.

Expected behavior

Schedule / 16 range.

Current behavior

Informs that it is not a valid entry.

@y0urself
Copy link
Member

y0urself commented Oct 5, 2020

What command/script are you using that is related to the gvm-tools?

@arkhelieldan
Copy link
Author

arkhelieldan commented Oct 5, 2020

Hi, i`m not using script.
I read in this topic about increase scan of gvmd: https://community.greenbone.net/t/gmp-scanner/2050/22 and https://lists.wald.intevation.org/pipermail/openvas-discuss/2016-June/009701.html
But i dont know to use this in docker to scan /16 range.

@y0urself
Copy link
Member

y0urself commented Oct 6, 2020

Do you think this is a bug or a missing feature to any of Greenbone's components or are you looking for the answer to an usage issue?
Maybe you can find help in the community, you already linked?

@y0urself
Copy link
Member

y0urself commented Oct 8, 2020

This issue is not related to gvm-tools at all.
Maybe you can try to setup our environment on your own, instead of using third party dockers.

@y0urself y0urself closed this as completed Oct 8, 2020
@y0urself y0urself added the invalid This doesn't seem right label Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants