/pɪŋ ɡəˈnuː/
Pingnoo is an open-source combined traceroute and ping application for analysing network connections. It runs under Windows, Mac OS and Linux.
The binaries are available under the releases page.
Download the installer executable and run to install the application. This will create a shortcut which is used launch the software.
The portable edition is supplied as a zip file which can be unzipped onto a memory stick, the application can be launched directly from the memory stick without the need to install the software.
The application is a dmg disk image. Download and open the disk image and drag the Pingnoo icon into the Applications folder, the application can then be launched by double-clicking on the Pingnoo icon in Applications.
Native packages for popular Linux distributions are available, and these install with the correct permissions, which allow the application to run without root permissions.
Pingnoo is available pre-built for the following versions.
- Debian 10
- Ubuntu 18.04, 20.04, 20.10
- Raspbian 10
pingnoo can be installed on a supported operating system version via apt, in order to do this you will need to add the apt repository and gpg key, the follow command can be used to add the pingnoo repository to your installation.
curl -s https://packagecloud.io/install/repositories/nedrysoft/pingnoo/script.deb.sh | sudo bash
Once the repository is added, you can then install pingnoo with the following command:
sudo apt install pingnoo
By using the apt repository, you will be able to update pingnoo easily with:
sudo apt update
Alternatively, you can download the appropriate deb file and install manually:
dpkg -i <downloaded file>.deb
apt -f install
Pingnoo is available pre-built for the following versions.
- Fedora r32
- Fedora r33
pingnoo can be installed on a supported operating system version via yum, in order to do this you will need to add the rpm repository and gpg key, the follow command can be used to add the pingnoo repository to your installation.
curl -s https://packagecloud.io/install/repositories/nedrysoft/pingnoo/script.rpm.sh | sudo bash
Once the repository is added, you can then install pingnoo with the following command:
sudo yum install pingnoo
By using the yum repository, you will be able to update pingnoo easily with:
sudo yum update
Alternatively, you can download the appropriate rpm file and install manually:
yum localinstall <downloaded file>.rpm
Pingnoo is available in the AUR.
You can also clone the project from the AUR and build and install manually.
git clone https://aur.archlinux.org/pingnoo.git
cd pingnoo
makepkg
sudo pacman -U <filename>.zst
Alternatively, You man also use a tool such as yay to install.
yay -S pingnoo
The application is also provided as an AppImage, an AppImage bundles all dependencies and therefore will run on any modern Linux distribution.
After downloading the AppImage, you then need to do the following:
chmod +x <downloaded filename>
The application requires RAW socket access, and this means some limitations created by the AppImage process affect the operation of the application. You will need to follow the instructions outlined in the Linux Notes section regarding setuid; this will allow you to run the application directly. Alternatively, you can launch from the terminal by using:
sudo ./<downloaded filename>
Documentation can be found on https://pingnoo.readthedocs.io/en/latest/
To build pingnoo from source, the following requirements must be satisfied
- Qt 5 libraries
- CMake for building the application
Pingnoo uses a modular design architecture based on components (aka plugins); the software can be extended easily by third parties by creating new components or modifying existing ones.
The following compiler configurations are known to work for development. (We do not supply binaries for 32-bit systems)
- Linux - 32 & 64-bit using GNU g++
- Windows - 32 & 64-bit using MSVC 2019 Community Edition
- Windows - 32 & 64-bit using mingw-g++
- Mac OS - 64-bit using clang from the xcode command line tools
Building the project will require certain libraries and toolchairs to be installed, the instructions below should be used as a guide for setting up a build environment.
The source can be obtained using Git.
git clone https://github.com/nedrysoft/pingnoo.git
cd pingnoo
git submodule update --init --recursiveThe build documentation contains information about packages that are required to build the software from source.
Change to the folder that contains the source code, and then execute the following commands.
mkdir build
cd build
cmake ..
makeThe software will be configured and the resulting binaries can be found in ../bin//
For example, an x86_64 Release build would be located at ,,/bin/x86_64/Release
Change to that folder and execute ./Pingnoo to run the application.
The deploy.py python script creates runnable/installable binaries for the given operating system.
- Linux - Generates a stand-alone AppImage and distribution specific packages.
- Windows - Generates an installer and a portable zip file which can run from a USB stick.
- Mac OS - Generates a DMG file.
The script requires Python 3.6 or later, curl and the colorama python module to enhance the console output. You can install the Colorama module with the following command.
(The CMake script provides an install target which uses the deploy script and will generate the appropriate deployable image for the platform being used.)
pip3 install colorama
The script provides the following parameters:
--qtdir="<path to qt>"- the path to the version of qt used.--curlbin="<path to curl binary>"- the path to the curl binary, i.e"/usr/bin/curl".--arch="<x64|x86|universal>"- the architecture to deploy. (universal is available on macOS and Windows)--type=<release|debug>- the build type to deploy.--cert="<cert>"- the value of this is dependent on the platform, for Windows and Mac OS it is the name of the certificate to be used, for Linux it is the gpg2 key identifier.--timeserver="<name>"- windows only, the name of the time server to be used during signing--appleid="<email>"- Mac OS only, the Apple ID of the developer account used to sign the binary--password="<password>"- Mac OS only, the password of the Apple ID. The password can be stored in the keychain and accessed using"@keychain:<identifier>"instead of passing the actual password to the script.--appimage- Linux only, will generate an AppImage.--rpm- Linux only, will generate an rpm package.--deb- Linux only, will generate a deb package.--pkg- Linux only, will generate an arch package.--appiamagetool="<path to appimage tool"- Linux only, the path to the appimagetool binary.--linuxdeployqy="<path to linuxdeployqt tool"- Linux only, the path to the linuxdeployqt binary.--signtool="<path to sign tool>"- Windows only, the path to the signing tool.--pin=<pin>- Windows only, if using scsigntool, the pin to use.--portable- Windows only, will generate a portable zip file for windows.--version- the version of the deployment tool.--debugoutput- produce debug output.
The script will use the curl binary to obtain any tools required for the deployment process.
The script stores the deployable asset in the deployment folder.
The PingCommandPingEngine ping engine is an experimental ping engine that uses the linux system ping command, this allows the software to run without any special privileges.
If the ICMPPingEngine is selected, then the application will require RAW socket privileges and therefore must be run as root or given raw socket access using the setcap* command.
The setcap comamnd will not work on the AppImage linux release as the privileges will not propagate down into the AppImage when it is mounted via fuse.
The CMake configuration for Linux has the following post link command, this command is optional, and you can control this with the option Pingnoo_SetRawCapabilities.
sudo -n /usr/sbin/setcap cap_net_raw,cap_net_admin=eip $${APPLICATION_BINARY_FOLDER}/$${TARGET}
This command will automatically apply the privileges to the executable after linking by running setcap via sudo, the flag -n is required to stop sudo prompting for a password if necessary if a password is needed then sudo will fail.
To stop sudo requesting a password for the /usr/sbin/setcap command create the following entry in /etc/sudoers(replacing with the name of your user account):
<username> ALL = (root) NOPASSWD: /usr/sbin/setcap
Note that in some linux distributions setcap is located in /sbin.
Please be aware of any security issues by doing this.
Also, it's not possible to debug the application due to the requirement of RAW sockets, one way of solving this is to create a script in /usr/bin/gdb-sudo with the following content:
#!/bin/sh
sudo -n /usr/bin/gdb $@
Create an entry in /etc/sudoers to allow gdb to run as root without a password:
<username> ALL = (root) NOPASSWD: /usr/bin/gdb
The final step is to configure Qt Creator to use this proxy script. Create a new debugger configuration in Qt Creator selecting /usr/bin/gdb-sudo as the gdb binary. You can choose this script as the active debugger in any Qt kit that you wish to use for debugging.
Please be aware of any security issues by doing this.
Debugging memory leaks can be done with Valgrind, but as above the application requires raw socket privileges and Valgrind cannot run the executable without being run as root. The following command can be executed from the application binary folder to run Valgrind and produce an XML debug log. In QtCreator you can load this log for viewing. (For convenience a valgrind.sh script has been provided)
sudo /usr/bin/valgrind --child-silent-after-fork=yes --xml=yes --smc-check=all-non-file --tool=memcheck --gen-suppressions=all --track-origins=yes --leak-check=summary --num-callers=25 --xml-file=./debug.xml ./Pingnoo_debug
The primary mechanism of finding memory leaks is done with the Deleaker tool, it's currently Windows only, but works incredibly well for finding leaks.
The user interface is simple and allows viewing the stack trace of the leak which is invaluable when figuring out which level of code is responsible for the leak.
During development of modules, leaks often occur as code changes can be fluent, a tool like deleaker is essential for tracking these and it's a time saver not to worry about leaks during the initial coding phase knowing that you can easily and quickly fix them after development of the feature is complete.
Set the Pingnoo_Build_Tests option to ON to generate a binary which performs unit tests.
The user interface uses a Ribbon style toolbar (as seen in applications such as Microsoft Office). To build the designer plugin set the CMake option Pingnoo_Build_RibbonDesignerPlugin to ON, this will create the plugin in the bin folder which you will then need to copy to the Qt plugins folder.
The gatekeeper requirements in Mac OS mean that the application needs to be signed and notarised to run without user interaction for allowing the application to run. You will require a full developer account to obtain a code signing certificate that is valid for gatekeeper authentication.
This project was created and maintained by Adrian Carpenter.
I thank the following people for contributing to the project:
Pingnoo uses the following third-party libraries/assets/tools/services in the development of Pingnoo.
- Qt - cross platform framework, licensed under the GPLv3 licence.
- cmake - cross platform project build system, licensed under BSD licence.
- Catch2 - unit testing framework, licensed under the BSL-1.0 licence.
- GSL - guidelines support library for C++, licensed under the MIT licence.
- Font Awesome - glyph based icon font, licensed under the SIL OFL 1.1 licence.
- QCustomPlot - charting library for Qt, licensed under the GPLv3 licence.
- macdeployqtfix - finishes the job that macdeployqt starts, licensed under the MIT licence.
- linuxdeployqt - creates deployable linux binaries, licensed under the GPLv3 licence.
- create-dmg - automates the creation of Mac OS DMG files, licensed under the MIT licence.
- colorama - python module for terminal colour, licensed under the BSD licence.
- rapidfuzz-cpp - an implementation for fuzzy string matching, licensed under the MIT licence.
- gren - a tool for automating release notes, licensed under the GPLv3 licence.
Also, Pingnoo was developed using the following commercially licensed tools/services.
- SmartCard Tools - code-signing tool, allows automation of signing using a smartcard token.
- Certum Code Signing Certificate - open-source code signing certificate for signing Windows binaries.
- AdvancedInstaller - Installer creator for windows, License kindly provided by them for free.
- Affinity Designer - Vector artwork design application.
- Affinity Photo - Bitmap artwork design application.
- CLion - The C++ IDE Pingnoo is developed in, the license was kindly provided for free for the project.
- Deleaker - A memory leak detector for Windows, the license was kindly provided for free for the project.
- Icofx - A tool for producing icon & icns files from source images.
- packagecloud - packagecloud kindly host the package repositories for debian, ubuntu and fedora that make installing on those operating systems very easy.
This project is a grateful recipient of a micro-grant from icculus who provide micro-grants each year to open-source projects.
Pingnoo is open source and released under the GPLv3 License
Distributed as-is; no warranty is given or implied.