Can’t find your answer you're looking for? Try searching our database.

Nipper FAQs

Our licensing works on a per device basis by associating a device usage to an audited configuration. Once the device usage has been assigned to a device you will not be able to reallocate the usage, but you will be able to audit this device for the entirety of your subscription. If you have multiple year licenses, these device usages will be reset one year from the license creation date.
If upgrading to Nipper 2.4 and above, you will need to completely remove any previous Nipper installation from your system.

To completely remove Nipper from a Mac the following commands will need to be run;

sudo rm -rf /usr/bin/nipper*
sudo rm -rf /usr/lib/libnipper*
sudo rm -rf /usr/local/bin/nipper*
sudo rm -rf /Library/Frameworks/Qt*
sudo rm -rf /Library/Frameworks/libnipper*
sudo rm -rf /Applications/Nipper\ Studio.app/
sudo rm -rf ~/Library/Preferences/com.titania.*
If you have purchased the software you can audit a licensed device using Nipper as many times as you need to during your subscription period (we offer one, two, or three year options).

If using an evaluation license, you are able to audit a licensed device as many times as you need to within your 30-day trial.
As referred to in the license, a device is an individual workstation, firewall, router, or switch that Nipper will audit. If, for example, you have a management system that combines the configurations from five individual firewalls, you will need a five-device license to cover them all. If you have a switch stack with a single configuration it will count as a single device.

Virtual devices are treated the same as physical devices, requiring a device license for each individual device. For example, a Palo Alto device with three different virtual devices on it will require a four device license to audit all the configurations.
You can set up an account on the website and select Evaluate to trial Nipper for two devices over a period of one month. If you have any issues acquiring an evaluation license contact sales@titania.com.

Evaluation licenses are a one-time activation. During the installation if administrative credentials are used, at the point where prompted to input a license, select Continue then close Nipper. Following this, open Nipper, go to license manager and add a license there with the local user’s credentials.

When adding a license during the installation with administrative credentials, the license will be associated with the administrative account and not the local user.
Nipper licenses include all updates and upgrades during the license subscription. You can now download the software from your account area on the Titania website. Simply login to your account at https://www.titania.com.

Following the input of credentials, then click Log In. Now you have access to your account. Once logged in, click My Account and scroll down to the license section.

Here you can see a list of your licenses. Click the blue download files button next to your license for the download process to begin.

After clicking the blue download button, you can then select the version of Nipper / Paws you would like to download e.g. Windows, Mac, or Linux and then click the blue download button once more. Following this, your download should be ready for installation.
Installing and activating Nipper on multiple workstations allows users to access the license to audit devices across different teams, departments or locations.

When activating Nipper on multiple workstations we suggest that you set the update check to happen on every use, to monitor the device usage accurately.

To change the update settings, click on Change Settings on the Home page of Nipper. Then go to Options > Maintenance > Updates > Check Interval dropdown menu.
If Nipper does not recognise an imported configuration then error code "Processing wrong type of file" occurs.

This means that Nipper has processed the configuration file but was unable to identify some configuration settings that it would expect to find for a specific type of device. This can indicate that the configuration may have been retrieved in an unexpected format. To retrieve the configuration in the expected format, instructions can be found in the Nipper documentation tab, or within the Nipper Software via Help & Information > How do I get the configuration from my network device?

For example, when removing a version line from a configuration file that would usually contain version information this may occur. This feature helps to prevent situations such as processing a Juniper SRX configuration as a Cisco ASA device.

If you are sure that the configuration file is from the correct type of device, you could force Nipper to process it and ignore the fact that the usual settings were not present. This can be achieved using the force command line option when using the command line tool.