Features / In Use
The cloud interface of Fingbox is set up very intuitively and integrates well with Fing's mobile applications. All top level host information, such as IP address, Hostname, MAC address and vendor are backed up from Fing to the cloud. Additionally, any customizations such name, icon, notes, location, and tags can also be backed up from Fing to the cloud. If changes are made within Fingbox, you can choose to have the changes synched back to your mobile client.
Figure 3: The host information screen within Fingbox
You can also choose to alert on network status changes in either the mobile application or in the Fingbox cloud interface and your changes will synchronize. Status changes can also be set up to watch and alert for any new hosts on the network. Alerts are simply sent to the email address that was used to sign up for Fingbox. I was not able to determine if additional contacts could be set up for alerts.
Figure 4: The Fingbox cloud interface main screen
Two things were missing from Fingbox, which were present in Fing that I would have really liked to see. The first is the port scan information from the mobile client. While it may not be ideal to port scan each device on the network, it would be nice to have visibility in the cloud interface to any port scans that may have been run manually. If the information has already been captured, I believe it would add value to see it in the web interface.
Figure 5: Results of a port scan within the Fing mobile interface
The second feature that I was sad to see not integrated was the Wake on LAN function. This may be more of feature for managing a home office network vs. a larger office network, given the "always on" nature of business networks. I did not run a port sniffer against the Fing Sentinel to see if the communication was one-way or full duplex. But the cloud interface does provide an option to "Sync customizations", so I assume there is a mechanism to contact the Sentinel from the cloud interface.
I had a few small grievances with the web interface. The first was that my hosts spanned multiple pages, which is expected. However, when I saved changes to a host on the third page, I was returned to the first page. This has the potential to get tedious rather quickly if you are making lots of changes on pages deeper than the initial page. I would have liked to stay on the page where I was working after saving changes.