Installation

Download the appropriate file (checking system and architecture) from the Downloads page at lidecoder.com. Follow the instructions below to set your system up so that the scripts can be run from any directory.

Windows

Unzip the downloaded file in any directory. This will produce the directory limc-windows. All scripts can be run inside that directory. To make life easier you can add the limc-windows directory to your PATH so that the scripts can be run from anywhere:

- In Search, search for and then select: Advanced System Settings
- Click Environment Variables.
- Find the PATH environment variable and select it. Click Edit.
- Click New to add to the PATH.
- Enter the full path to the limc-windows directory
- Press OK

Open a new terminal and check that you can run the scripts, both cli and GUI:

lilicense -v
lilicense

Linux & Similar *nix-based OS

GLIBC 2.27 or later is required. To check the glibc version used by your distro release, run:

ldd --version ldd

Support for the GUI tools in Linux & Unix is best effort. The exact packages needed to launch the GUI can vary depending on the OS. We have tried to include all the necessary packages (which is why the Linux packages are so large). But in some cases, only the command line tools will work.

There are two options for *nix-based Operating Systems. For rpm-based distros for which you have administrator access (root login or sudo) you can install the rpm as in the section: RPM-Based Distros with Admin Access. Otherwise, continue with this section to install from the portable tar.gz file.

Untar the file:

tar -xzvf limc-linux-2.6.2.tar.gz

You can then run the scripts inside the resulting limc_linux directory. To run the scripts from everywhere, if you don’t have sudo or root access, append the absolute path to limc_linux to your shell’s PATH. To do this for bash for the current user run this command from the same parent directory of limc_linux (the one where you ran the tar command above):

echo "PATH=\$PATH:$(pwd)/limc-linux" >> $HOME/.bashrc

Alternatively, if you have root or sudo access you can do the following:

for script in liserver lidecode lilicense lishark load_ipsec_keys; do
   sudo ln -fs $(pwd)/limc-linux/$script /usr/bin
done

Open a new terminal and check that you can run scripts from anywhere:

lilicense -v

RPM-Based Distros with Admin Access

You can install the rpm file on an rpm-based distro for example: Fedora, Red Hat Enterprise Linux and SUSE Linux.

The three most common package managers for rpm files are dnf, yum and zipper. For Fedora and Red Hat use yum:

sudo yum localinstall limc-2.6.2-1.x86_64.rpm

These distros are transitioning towards using dnf as default so you may need to use that for more recent releases:

sudo dnf localinstall limc-2.6.2-1.x86_64.rpm

For SUSE Linux use zypper:

sudo zypper install limc-2.6.2-1.x86_64.rpm

The rpm will automatically set up the links so that the scripts can be run from anywhere. Test with:

lilicense -v

Note that most of the RPM dependencies are needed only for the GUI. If you are unable to install some of the dependencies, you can try to ignore them and in most cases you will still be able to run the tools from command line.

Installing tshark

The lishark script needs a local install of tshark, the command line version of wireshark.

For Windows, simply install wireshark, and select to also install tshark during installation.

For Linux, install wireshark with your package manager. Tshark is usually included but if not install it separately. They are almost always in the default repositories for your Operating System and on the installation dvd.

To check the tshark install:

tshark -v

Tshark V4 minimun is preferred as it provides the ‘matches’ keyword which is used by lishark and provides more reliable filtering. Tshark V3 will work with almost the same level of functionality.

After installing tshark it is usually needed to add your user to the wireshark group if you wish to run live captures:

sudo usermod -a -G wireshark $USER

For some OS releases there will still be a permission denied error when running live captures. In that case the following command may also be needed:

sudo chmod +x /usr/bin/dumpcap