[ZBXNEXT-1330] Nmap host specific subnet scanning and discovery Created: 2012 Jul 24 Updated: 2012 Nov 22 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Joris Lambrecht | Assignee: | Alexei Vladishev |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | networkdiscovery | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Any operating system running nmap |
||
| Description |
|
While performing discovery for a network there is found a blocking limitation. Scanning for a subnet is not efficient when scanning for a network-range such as IP.IP.IP-IP.IP ( 10.10.1-255.1 ), in this example it is used to scan for gateways supporting snmp, ssh, http, https and responding to icmp. If this matches there is a router or switch present and it should be monitored. This can easily be done using nmap but the input type is not supported in zabbix which only permits IP.IP.IP.IP-IP not a variation on this. If using nmap from zabbix is permitted in such way this has not been documented. I could not find a page that documented how to make a script for this with nmap. Especially since the input type validates against IP.IP.IP.IP-IP |
| Comments |
| Comment by Joris Lambrecht [ 2012 Jul 31 ] |
|
If there is any code-related testing i can do on my side i'd very much appreciate any feedback to set my on my way to resolve this issue. |
| Comment by Alexei Vladishev [ 2012 Oct 13 ] |
|
I think it should be implemented by allowing extensions for auto-discovery based on external scripts. |