AppImages > Network > jsNetMonitor


jsNetMonitor

Screenshot of jsNetMonitor

jsNetMonitor shows the traffic of every network connection of your computer live — cable, Wi-Fi, mobile, bundled connections, bridges, VLANs and VPN tunnels — in the look of a studio rack.

  • Download and upload of each device, as smooth curves and level meters
  • Which program uses the network, and how much
  • Every connection with remote host, country, service, state, speed and latency
  • Where your traffic goes: destinations and countries at a glance
  • Your total traffic over minutes, hours, a week, a month or a whole year
  • Traffic per day and month, kept across restarts
  • The network chip, its driver, firmware and link details
  • A small minimal view that stays on top
  • Arrange the device units as you like — the layout is remembered
  • Lists you can sort, widen and trim to the columns you need
  • Light and dark, in 83 languages

Compatibility: Uses the C library of the system (may need glibc 2.34 or later)


Usage

jsNetMonitor is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. Awesome!

AppImages are single-file applications that run on most Linux distributions. Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions.

This AppImage uses the C library of the system and may need glibc 2.34 or later. It does not run on distributions that use a different C library (such as musl on Alpine Linux) or an older glibc.

Running jsNetMonitor on Linux without installation

Unlike other applications, AppImages do not need to be installed before they can be used. However, they need to be marked as executable before they can be run. This is a Linux security feature.

Beware! AppImages are usually not verified by others. Follow these instructions only if you trust the developer of the software. Use at your own risk!

Download the jsNetMonitor AppImage and make it executable using your file manager or by entering the following commands in a terminal:

chmod +x ./*.AppImage

Then double-click the AppImage in the file manager to open it.

Sandboxing jsNetMonitor

If you want to restrict what jsNetMonitor can do on your system, you can run the AppImage in a sandbox like Firejail. This is entirely optional and currently needs to be configured by the user.

Updating jsNetMonitor

If you would like to update to a new version, simply download the new jsNetMonitor AppImage.

The jsNetMonitor AppImage also can be updated using AppImageUpdate. Using this tool, jsNetMonitor can be updated by downloading only the portions of the AppImage that have actually changed since the last version.

Integrating AppImages into the system

If you would like to have the executable bit set automatically, and would like to see jsNetMonitor and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon.


Note for application authors

Thanks for distributing jsNetMonitor in the AppImage format for all common Linux distributions. Great! Here are some ideas on how to make it even better.

Pro Tips for further enhancing the jsNetMonitor AppImage

Please consider making the jsNetMonitor AppImage self-contained, so that it does not depend on the C library of the system and runs on more distributions: ship the C library including its loader (ld-linux-*.so.*) and use it to launch the application, or link statically.

Thanks for shipping AppStream metainfo inside your AppImage. Please open a pull request on https://github.com/AppImage/appimage.github.io/blob/master/data/jsNetMonitor if you have changed it and would like to see this page updated accordingly.

If you would like to see a donation link for the application here, please include one in the AppStream data.

History of this page

Edit the input for this page