How to run a network discovery?

An administrative user account is required to run the software on all platforms.
The network discovery provides a complete view of any network: fing engine automatically detects the underlying network type and uses the best technique to take the picture of the target network.

The best results are achieved on Local Area Networks, both on wired Ethernet connection and wireless Wi-Fi connections, where Fing can make use of the dedicated data-link layer discovery engine which is faster and more accurate. Fing’s engine can detect all the hosts present in the network, even behind a Firewall!

Discoveries performed on non-local networks (or non-ethernet networks) are handled by a network layer discovery engine, which relies on TCP/IP network layer, i.e. ICMP (ping) and TCP queries. When you start a discovery fing tells you the actual engine which is being used; in case of specific needs, it is possible to configure and tune each engine for optimal results, creating dedicated discovery profiles in the related configuration properties file:

When you start Fing without arguments, it takes the nearest of your available networks and starts performing a discovery on it, reporting stuff directly on console. But you can perform discovery on any network, by providing your target network to fing in the command line:

 <cmd> -n<cmd> -n

If you do not provide any output parameter, fing uses default ones (as specified in its configuration file). But for a running discovery you can setup as many output formats as you need, by providing a command line argument like:

 <cmd> -o setupFormat1 setupFormat2 ... setupFormatN

The output format setup syntax is pretty simple: there are 2 main categories of output flows, table and log. The table flow produces a network table dump every time a discovery round is completed, while the log flow logs each network event as soon as it’s detected.

If you want to change the discovery round frequency, edit the related round.interval setting in configuration file. Note that for each profile you declare you must provide both configurations for data-link and network layer discovery classes.

The log flow allows you to log network events in real-time, on the console itself or in a specific file. Currently there are two formats supported for log flows: text and CSV.

E.g. to start fing producing textual log in console and a CSV log in a file:

 <cmd> -o log,text log,csv,my-network-log.csv

The table flow instead produces a network table view refreshed each time a discovery round finishes. The most popular formats are text and HTML but here it is the complete list: stext (short text for 80-columns console), text (plain text), html, csv, and xml.

E.g. on Windows to make fing report network discovery to an HTML file on your:

 fing -o table,stext table,html,"%USERPROFILE%\Desktop\network.html"

The network table report contains details for each host found in the network, and it’s refreshed in real-time at each round: IP address, MAC address, hostname and host friendly name. The latter is a friendly name you can associate to the hosts by means of the configuration file, where you are able to define your custom names for hosts (by IP address or MAC address) and for networks.

By default, when you close fing the discovery session is lost, unless you want to save session data into a session file; in this case fing can be closed and restarted when you need, without losing any discovery session data. To exploit discovery session feature you have to simply provide fing the session file name to use.

E.g. on Windows to make fing generate an HTML report and save session data in a folder named report:

 fing -n -o table,html,c:\report\lan.html --session                c:\report\lansessiondata

Was this article helpful?

Related Articles