Lansweeper report number of assets per subnet

#Lansweeper report number of assets per subnet full#
#Lansweeper report number of assets per subnet windows#

The nmap.sh or nmap.cmd scripted input can be run directly from the command line for testing. Only those network connection which are initiated by nmap for the purpose of scanning. Targets should be prefixed with a '-t' switch per the example. A '-oG' option will be automatically inserted in order to force the 'Grepable' format. You should be able to pass in any standard nmap arguments. You can have a single scan which has many targets, per the previous example, or you may create new inputs for each in the event that you'd like to stagger their execution, etc. For a port scan of 2 subnets, something like: /opt/splunk/demo/etc/apps/asset_discovery/bin/nmap.sh -A -O -t 10.159.26.0/24 -t 10.59.27.0/24) and leave the remaining fields alone, click 'Save'. Enter the proper command for your situation (e.g. Find the appropriate input and 'Clone' it. There should be 4 results, a ping scan and port scan for *nix, and the same for Windows. the scan point) head to Manager -> Data Inputs -> Scripts and search for 'nmap'. Knowing that, from your Splunk instance (i.e. There are 2 types of inputs for this app: ping scans and port scans. In the event that you'd prefer to have a small number of scan points which will scan multiple networks you'll need to create some custom data inputs. In order to set a target, use the '-t' option (not a standard nmap option). You may pass standard nmap arguments through in order to perform a port scan.

With no arguments given, the scripted input will perform a ping scan of the local subnet of the current system: This behavior can be overriden by passing a '-t target_spec' argument to the script.

In this way, the app can be deployed to remote forwarders to regularly scan the forwarder's subnet, without having to configure the target for each individual forwarder. The scripted input will attempt to find the current host's IP address and, if no other target is given, use that IP to perform a scan of the local subnet. The included scripted input will automatically include the necessary argument for 'Grepable' output format as defined by. This app utilizes a scripted input, nmap.sh or nmap.cmd, to execute nmap scans of (hopefully) any type. Running as a standard user will most likely yield unexpected results. Additionally, the nmap binary works best if it is run as root. It assumes that the command is available and in the path. This app utilizes the nmap command, but does not provide it. All searches have been created to use eventtypes which reference index=asset_discovery which can easily be overriden depending on your needs. This app utilizes its own 'asset_discovery' index.

#Lansweeper report number of assets per subnet windows#

The Windows scripts are lightly tested, please report bugs. If you do not do this, the input will fail. There is an example_nmap.path in the bin directory.

#Lansweeper report number of assets per subnet full#

Notes on the Windows scripted input, nmap.cmd (which calls nmap.vbs): You must create the file bin map.path which contains the full path to your nmap.exe (i.e. Please let me know if you encounter this issue. More information and a fix can be found here. If you are not receiving scan data and you're sure that everything is enabled and setup properly, it's quite possible that you're just being affected by this. The latest version of Splunk seems to have changed something in the way LD_LIBRARY_PATH is handled. Developed by: Mike Wilson (mwilson at ) Noteworthy