[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5477":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":31,"readmeContent":32,"aiSummary":33,"trendingCount":16,"starSnapshotCount":16,"syncStatus":34,"lastSyncTime":35,"discoverSource":36},5477,"bandwhich","imsnif\u002Fbandwhich","imsnif","Terminal bandwidth utilization tool","",null,"Rust",11806,343,75,33,0,4,27,73,30,42.61,"MIT License",false,"main",true,[27,28,29,30],"bandwidth","cli","dashboard","networking","2026-06-12 02:01:10","# bandwhich\n\n![demo](res\u002Fdemo.gif)\n\nThis is a CLI utility for displaying current network utilization by process, connection and remote IP\u002Fhostname\n\n## Table of contents\n\n- [bandwhich](#bandwhich)\n  - [Table of contents](#table-of-contents)\n  - [Project status](#project-status)\n  - [How does it work?](#how-does-it-work)\n  - [Installation](#installation)\n    - [Downstream packaging status](#downstream-packaging-status)\n    - [Download a prebuilt binary](#download-a-prebuilt-binary)\n  - [Building from source](#building-from-source)\n    - [Cross-compiling](#cross-compiling)\n      - [Android](#android)\n  - [Post install (Linux)](#post-install-linux)\n    - [1. `setcap`](#1-setcap)\n      - [Capabilities explained](#capabilities-explained)\n    - [2. `sudo` (or alternative)](#2-sudo-or-alternative)\n  - [Post install (Windows)](#post-install-windows)\n  - [Usage](#usage)\n  - [Contributing](#contributing)\n  - [License](#license)\n\n## Project status\n\nThis project is in passive maintenance. Critical issues will be addressed, but\nno new features are being worked on. However, this is due to a lack of funding\nand\u002For manpower more than anything else, so pull requests are more than welcome.\nIn addition, if you are able and willing to contribute to this project long-term,\nwe would like to invite you to apply for co-maintainership.\n\nFor more details, see [The Future of Bandwhich #275](https:\u002F\u002Fgithub.com\u002Fimsnif\u002Fbandwhich\u002Fissues\u002F275).\n\n## How does it work?\n\n`bandwhich` sniffs a given network interface and records IP packet size, cross referencing it with the `\u002Fproc` 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.\n\n## Installation\n\n### Downstream packaging status\n\nFor detailed instructions for each platform, see [INSTALL.md](INSTALL.md).\n\n\u003Ca href=\"https:\u002F\u002Frepology.org\u002Fproject\u002Fbandwhich\u002Fversions\">\n  \u003Cimg src=\"https:\u002F\u002Frepology.org\u002Fbadge\u002Fvertical-allrepos\u002Fbandwhich.svg?columns=3\" alt=\"Packaging status\">\n\u003C\u002Fa>\n\n### Download a prebuilt binary\n\nWe offer several generic binaries in [releases](https:\u002F\u002Fgithub.com\u002Fimsnif\u002Fbandwhich\u002Freleases) for various OSes.\n\n\u003Ctable>\n  \u003Cthead>\n    \u003Cth>OS\u003C\u002Fth>\u003Cth>Architecture\u003C\u002Fth>\u003Cth>Support\u003C\u002Fth>\u003Cth>Usage\u003C\u002Fth>\n  \u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr>\n      \u003Ctd>Android\u003C\u002Ftd>\u003Ctd>aarch64\u003C\u002Ftd>\u003Ctd>Best effort\u003C\u002Ftd>\n      \u003Ctd>\n        \u003Cp>All modern Android devices.\u003C\u002Fp>\n        \u003Cp>Note that this is a pure binary file, not an APK suitable for general usage.\u003C\u002Fp>\n      \u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd rowspan=\"3\">Linux\u003C\u002Ftd>\u003Ctd>aarch64\u003C\u002Ftd>\u003Ctd>Full\u003C\u002Ftd>\n      \u003Ctd>64-bit ARMv8+ (servers, some modern routers, RPi-4+).\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd>armv7hf\u003C\u002Ftd>\u003Ctd>Best effort\u003C\u002Ftd>\u003Ctd>32-bit ARMv7 (older routers, pre-RPi-4).\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd>x64\u003C\u002Ftd>\u003Ctd>Full\u003C\u002Ftd>\n      \u003Ctd>Most Linux desktops & servers.\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd rowspan=\"2\">MacOS\u003C\u002Ftd>\u003Ctd>aarch64\u003C\u002Ftd>\u003Ctd rowspan=\"2\">Full\u003C\u002Ftd>\n      \u003Ctd>Apple silicon Macs (2021+).\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd>x64\u003C\u002Ftd>\n      \u003Ctd>Intel Macs (pre-2021).\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\n      \u003Ctd>Windows\u003C\u002Ftd>\u003Ctd>x64\u003C\u002Ftd>\u003Ctd>Full\u003C\u002Ftd>\n      \u003Ctd>Most Windows desktops & servers.\u003C\u002Ftd>\n    \u003C\u002Ftr>\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n## Building from source\n\n```sh\ngit clone https:\u002F\u002Fgithub.com\u002Fimsnif\u002Fbandwhich.git\ncd bandwhich\ncargo build --release\n```\n\nFor the up-to-date minimum supported Rust version, please refer to the `rust-version` field in [Cargo.toml](Cargo.toml).\n\n### Cross-compiling\n\nCross-compiling for alternate targets is supported via [cross](https:\u002F\u002Fgithub.com\u002Fcross-rs\u002Fcross). Here's the rough procedure:\n\n1. Check the target architecture. If on Linux, you can use `uname -m`.\n2. Lookup [rustc platform support](https:\u002F\u002Fdoc.rust-lang.org\u002Frustc\u002Fplatform-support.html) for the corresponding target triple.\n3. [Install `cross`](https:\u002F\u002Fgithub.com\u002Fcross-rs\u002Fcross#installation).\n4. Run `cross build --release --target \u003CTARGET_TRIPLE>`.\n\n#### Android\n\nUntil [cross-rs\u002Fcross#1222](https:\u002F\u002Fgithub.com\u002Fcross-rs\u002Fcross\u002Fissues\u002F1222) is solved, use the latest HEAD:\n\n```sh\ncargo install --git https:\u002F\u002Fgithub.com\u002Fcross-rs\u002Fcross.git cross\ncross build --release --target aarch64-linux-android\n```\n\n## Post install (Linux)\n\nSince `bandwhich` sniffs network packets, it requires elevated privileges.\nOn Linux, there are two main ways to accomplish this:\n\n### 1. `setcap`\n\n- Permanently allow the `bandwhich` binary its required privileges (called \"capabilities\" in Linux).\n- Do this if you want to give all unprivileged users full access to bandwhich's monitoring capabilities.\n    - This is the **recommended** setup **for single user machines**, or **if all users are trusted**.\n    - This is **not recommended** if you want to **ensure users cannot see others' traffic**.\n\n```sh\n# assign capabilities\nsudo setcap cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep $(command -v bandwhich)\n# run as unprivileged user\nbandwhich\n```\n\n#### Capabilities explained\n- `cap_sys_ptrace,cap_dac_read_search`: allow access to `\u002Fproc\u002F\u003Cpid>\u002Ffd\u002F`, so that `bandwhich` can determine which open port belongs to which process.\n- `cap_net_raw,cap_net_admin`: allow capturing packets on your system.\n\n### 2. `sudo` (or alternative)\n\n- Require privilege escalation every time.\n- Do this if you are an administrator of a multi-user environment.\n\n```sh\nsudo bandwhich\n```\n\nNote that if your installation method installed `bandwhich` to somewhere in\nyour home directory (you can check with `command -v bandwhich`), you may get a\n`command not found` error. This is because in many distributions, `sudo` by\ndefault does not keep your user's `$PATH` for safety concerns.\n\nTo overcome this, you can do any one of the following:\n1. [make `sudo` preserve your `$PATH` environment variable](https:\u002F\u002Funix.stackexchange.com\u002Fq\u002F83191\u002F375550);\n2. explicitly set `$PATH` while running `bandwhich`: `sudo env \"PATH=$PATH\" bandwhich`;\n3. pass the full path to `sudo`: `sudo $(command -v bandwhich)`.\n\n## Post install (Windows)\n\nYou might need to first install [npcap](https:\u002F\u002Fnpcap.com\u002F#download) for capturing packets on Windows.\n\n## Usage\n\n```\nUsage: bandwhich [OPTIONS]\n\nOptions:\n  -i, --interface \u003CINTERFACE>      The network interface to listen on, eg. eth0\n  -r, --raw                        Machine friendlier output\n  -n, --no-resolve                 Do not attempt to resolve IPs to their hostnames\n  -s, --show-dns                   Show DNS queries\n  -d, --dns-server \u003CDNS_SERVER>    A dns server ip to use instead of the system default\n      --log-to \u003CLOG_TO>            Enable debug logging to a file\n  -v, --verbose...                 Increase logging verbosity\n  -q, --quiet...                   Decrease logging verbosity\n  -p, --processes                  Show processes table only\n  -c, --connections                Show connections table only\n  -a, --addresses                  Show remote addresses table only\n  -u, --unit-family \u003CUNIT_FAMILY>  Choose a specific family of units [default: bin-bytes] [possible values: bin-bytes, bin-bits, si-bytes, si-bits]\n  -t, --total-utilization          Show total (cumulative) usages\n  -h, --help                       Print help (see more with '--help')\n  -V, --version                    Print version\n```\n\n## Contributing\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## License\n\nMIT\n","bandwhich 是一个终端带宽使用情况监控工具，能够按进程、连接和远程IP\u002F主机名显示当前网络使用情况。它采用Rust语言编写，具备跨平台特性，支持Linux、macOS以及Windows系统，并且能够智能地根据终端窗口大小调整展示信息量。该工具通过监听指定的网络接口并结合不同操作系统下的文件系统或API来获取数据，同时尝试以最佳努力方式解析IP地址到对应的主机名。适用于需要实时掌握系统中各部分网络流量消耗情况的场景，如服务器运维、网络故障排查等。",2,"2026-06-11 03:03:32","top_language"]