Building and Installing RPM Packages for the Napatech Driver and Tools

Software Installation for Linux

Platform
Intel® PAC
Napatech SmartNIC
Content Type
Software Installation Guide
Capture Software Version
Link™ Capture Software 12.11

This chapter describes how to build and install RPM packages for the Napatech driver and tools from source RPM packages.

Sample SRPM packages

The product release package includes example source RPM (SRPM) packages for building binary RPM packages for the Napatech driver and tools.

Each SRPM package consists of the corresponding component package archive and an RPM spec file. You can use the SRPM packages as-is, or modify the spec files to suit your requirements.

The following SRPM packages are included:
  • nt-driver-3gd-x.y.z.build.short-sha1.src.rpm
  • nt-tools-3gd-x.y.z.build.short-sha1.src.rpm

The driver package includes unit configuration for integration with systemd based Linux distribution, for example Red Hat Enterprise Linux 7, CentOS 7 and Ubuntu 15.04 or later.

Package signature verification

The RPM packages are signed, and the associated public keys can be found on the Napatech Support Portal at: https://supportportal.napatech.com. The following command shows an example how to import the key.
$ sudo rpm --import RPM_GPG_KEY-NT_SW_GROUP
To list available keys, run the following command.
$ rpm -q gpg-pubkey --qf \\'%{name}-%{version}-%{release} --> %{summary}\n\\'
An output example:
gpg-pubkey-f4a80eb5-53a7ff4b --> gpg(CentOS-7 Key (CentOS 7 Official Signing Key))
gpg-pubkey-352c64e5-52ae6884 --> gpg(Fedora EPEL (7) )
gpg-pubkey-52bdea88-62bec77f --> gpg(Napatech A/S )
The packages can be verified using the provided keys. For example:
rpm --checksig nt-driver-3gd-3.26.1.168-28830046.src.rpm
An output example:
nt-driver-3gd-3.26.1.168-28830046.src.rpm: rsa sha1 (md5) pgp md5 OK
pgp in the output indicates that the digital signature in the package is a valid signature of the package file contents and was produced by the organization that originally signed the package.
Note: It is not required to verify the signature for installing and using the RPM packages. The reason that the RPM packages are signed is to ensure that they have not been modified since they were signed.