What can be a reason if on MacOS it does not capture traffic? I see empty panels. Tried to run with and without `sudo`.
yep, on macOS 10.14.6 the command starts but the panes stays empty (silent error) because of SIP "Sandbox: lsof System Policy: deny(1)"
What: A terminal tool to check what is taking up your bandwidth
181–190 of 190 posts
Re: What: A terminal tool to check what is taking up your bandwidth
#182Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)
The author has renamed this project to 'bandwhich'.
Re: What: A terminal tool to check what is taking up your bandwidth
#183I need this for windows.
I used to use Glasswire, however did not like the yearly subscription and limited interface. Now I use NetLimiter 4: https://www.netlimiter.com/ Among other features like process blocking, it has a process list not very different than this utility as well has bandwidth graphing over a period in time which is very useful in tracking down bandwidth hogs on a monthly capped DSL line. https://www.netlimiter.com/docs/netl…
Re: What: A terminal tool to check what is taking up your bandwidth
#184Re: What: A terminal tool to check what is taking up your bandwidth
#185Earlier quoted context omitted.
I’m using multiple search engines more and more. Possibly this is due to me usually bypassing google to avoid the ad laden hits. A view with search results from a few sources comes to mind as a solution. Another back burner project.
You can do this with browser search engines, but as a DuckDuckGo user, I can !bang search_term (`!gh`, `!github` to search in github.) Now, I think DuckDuckGo is very lacking in terms of Zero-click searching, but if I know where to get information I can !bang to it (e.g., `!hn what`) or if you're feeling luck `\hn what` will open the first search result. Much better than spending an afternoon setting up search engine…
Re: What: A terminal tool to check what is taking up your bandwidth
#186For some reason (possibly security limitations) it doesn't seem to be able to monitor connections over a WireGuard connection's tunX interface.
Would you be willing to open an issue in the github repo? I am not aware of this bug and would be very happy to address it.
I would especially be interested if this happens to be the same bug as: https://github.com/imsnif/bandwhich/issues/51
Thanks!
Re: What: A terminal tool to check what is taking up your bandwidth
#187Earlier quoted context omitted.
My complaint about the name is that it would be hard to "google" it. This means if I don't bookmark it or remember where I found it, then a couple of years from now when my laptop needs to be rebuilt, I'll have the darndest time finding it to install it again.
I just type in what I’m looking for and “news.ycombinator.com” at the end so that it links to a HN page. Sometimes I have to use site: to make sure it’s actually from HN, but works reasonably well.
Re: What: A terminal tool to check what is taking up your bandwidth
#188Earlier quoted context omitted.
Thanks for the tool. Easier install methods would be great. For now I've added the following to my bootstrap makefile: wget -qO- https://github.com/imsnif/what/releases/download/${WHAT_VERSION}/what-v${WHAT_VERSION}-x86_64-unknown-linux-musl.tar.gz | tar xvz -C ~/bin/
Care to share the bootstrap makefile?
It's a mess and I've not used it for a while (haven't setup a new computer lately) but gets the point across.
Re: What: A terminal tool to check what is taking up your bandwidth
#189Earlier quoted context omitted.
This is the main problem keeping me from using this right now. I don't like installing binaries that conflict with system package names because I'm tin foil about stability and the super small chance that some installation/config script for some other package I rely on references `what` and breaks. @imsnif 2 questions: 1. Any chance you'd be willing to rename the package? I get it if not, but that would be so dope. 2…
1. Done. It's now known as "bandwhich" 2. This is in progress: https://github.com/imsnif/bandwhich/issues/9
Re: What: A terminal tool to check what is taking up your bandwidth
#190Earlier quoted context omitted.
This is the main problem keeping me from using this right now. I don't like installing binaries that conflict with system package names because I'm tin foil about stability and the super small chance that some installation/config script for some other package I rely on references `what` and breaks. @imsnif 2 questions: 1. Any chance you'd be willing to rename the package? I get it if not, but that would be so dope. 2…
1. Done. It's now known as "bandwhich" 2. This is in progress: https://github.com/imsnif/bandwhich/issues/9