Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Terminal bandwidth utilization tool

License

NotificationsYou must be signed in to change notification settings

imsnif/bandwhich

Repository files navigation

demo

This is a CLI utility for displaying current network utilization by process, connection and remote IP/hostname

Table of contents

Project status

This project is in passive maintenance. Critical issues will be addressed, butno new features are being worked on. However, this is due to a lack of fundingand/or manpower more than anything else, so pull requests are more than welcome.In addition, if you are able and willing to contribute to this project long-term,we would like to invite you to apply for co-maintainership.

For more details, seeThe Future of Bandwhich #275.

How does it work?

bandwhich sniffs a given network interface and records IP packet size, cross referencing it with the/proc filesystem on linux,lsof on macOS, or using WinApi on windows. It is responsive to the terminal window size, displaying less info if there is no room for it. It will also attempt to resolve ips to their host name in the background using reverse DNS on a best effort basis.

Installation

Downstream packaging status

For detailed instructions for each platform, seeINSTALL.md.

Packaging status

Download a prebuilt binary

We offer several generic binaries inreleases for various OSes.

OSArchitectureSupportUsage
Androidaarch64Best effort

All modern Android devices.

Note that this is a pure binary file, not an APK suitable for general usage.

Linuxaarch64Full64-bit ARMv8+ (servers, some modern routers, RPi-4+).
armv7hfBest effort32-bit ARMv7 (older routers, pre-RPi-4).
x64FullMost Linux desktops & servers.
MacOSaarch64FullApple silicon Macs (2021+).
x64Intel Macs (pre-2021).
Windowsx64FullMost Windows desktops & servers.

Building from source

git clone https://github.com/imsnif/bandwhich.gitcd bandwhichcargo build --release

For the up-to-date minimum supported Rust version, please refer to therust-version field inCargo.toml.

Cross-compiling

Cross-compiling for alternate targets is supported viacross. Here's the rough procedure:

  1. Check the target architecture. If on Linux, you can useuname -m.
  2. Lookuprustc platform support for the corresponding target triple.
  3. Installcross.
  4. Runcross build --release --target <TARGET_TRIPLE>.

Android

Untilcross-rs/cross#1222 is solved, use the latest HEAD:

cargo install --git https://github.com/cross-rs/cross.git crosscross build --release --target aarch64-linux-android

Post install (Linux)

Sincebandwhich sniffs network packets, it requires elevated privileges.On Linux, there are two main ways to accomplish this:

1.setcap

  • Permanently allow thebandwhich binary its required privileges (called "capabilities" in Linux).
  • Do this if you want to give all unprivileged users full access to bandwhich's monitoring capabilities.
    • This is therecommended setupfor single user machines, orif all users are trusted.
    • This isnot recommended if you want toensure users cannot see others' traffic.
# assign capabilitiessudo setcap cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep$(command -v bandwhich)# run as unprivileged userbandwhich

Capabilities explained

  • cap_sys_ptrace,cap_dac_read_search: allow access to/proc/<pid>/fd/, so thatbandwhich can determine which open port belongs to which process.
  • cap_net_raw,cap_net_admin: allow capturing packets on your system.

2.sudo (or alternative)

  • Require privilege escalation every time.
  • Do this if you are an administrator of a multi-user environment.
sudo bandwhich

Note that if your installation method installedbandwhich to somewhere inyour home directory (you can check withcommand -v bandwhich), you may get acommand not found error. This is because in many distributions,sudo bydefault does not keep your user's$PATH for safety concerns.

To overcome this, you can do any one of the following:

  1. makesudo preserve your$PATH environment variable;
  2. explicitly set$PATH while runningbandwhich:sudo env "PATH=$PATH" bandwhich;
  3. pass the full path tosudo:sudo $(command -v bandwhich).

Post install (Windows)

You might need to first installnpcap for capturing packets on Windows.

Usage

Usage: bandwhich [OPTIONS]Options:  -i, --interface <INTERFACE>      The network interface to listen on, eg. eth0  -r, --raw                        Machine friendlier output  -n, --no-resolve                 Do not attempt to resolve IPs to their hostnames  -s, --show-dns                   Show DNS queries  -d, --dns-server <DNS_SERVER>    A dns server ip to use instead of the system default      --log-to <LOG_TO>            Enable debug logging to a file  -v, --verbose...                 Increase logging verbosity  -q, --quiet...                   Decrease logging verbosity  -p, --processes                  Show processes table only  -c, --connections                Show connections table only  -a, --addresses                  Show remote addresses table only  -u, --unit-family <UNIT_FAMILY>  Choose a specific family of units [default: bin-bytes] [possible values: bin-bytes, bin-bits, si-bytes, si-bits]  -t, --total-utilization          Show total (cumulative) usages  -h, --help                       Print help (see more with '--help')  -V, --version                    Print version

Contributing

SeeCONTRIBUTING.md.

License

MIT


[8]ページ先頭

©2009-2025 Movatter.jp