can the range input be anything other then x.x.x.x\n how about x.x.x.1-x.x.x.10 etc? tried all sorts of combos so far nothings worked. hopefully I didn't miss something in the docs.
thanks
tr
auto-discovery range question.
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: auto-discovery range question.
I believe that x.x.x.1-10 or x.x.x.0/24 are the only options that work presently. Is there a specific format you are looking to have work?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: auto-discovery range question.
so using this 10.110.0.14-20 I should scan hosts 10.110.0.14 thru 10.110.0.20 correct? For some reason its not working!
any ideas?
any ideas?
Re: auto-discovery range question.
when I go back and edit the scan target the following is in the box
10.110.0.40-60 10.110.0.40-60
that doesn't look right to me.
10.110.0.40-60 10.110.0.40-60
that doesn't look right to me.
Re: auto-discovery range question.
somehow i get the feeling the only method is the cidr based method which unfortuantely sucks.
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: auto-discovery range question.
I could have swore we discussed and patched in a resolve for non cidr notation, as nmap should allow that just fine. However doing testing I am running into the same issues. I will put in a bug report for this.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.