What: A terminal tool to check what is taking up your bandwidth • Hacker News Board

kgersen wrote: post #5

hnarn wrote: post #2

What are the main differences to something like nethogs or iftop?

it's trendy to reinvent the wheel with Rust ?

It certainly is, but there is a merit to `what` too, in a different way of presenting the data.

Re: What: A terminal tool to check what is taking up your bandwidth

#24

Post by psibi » Mon, Dec 30, 2019, 9:55 AM UTC

adimitrov wrote: post #18

plmu wrote: post #17

Installation with yay/crate can be slow. This small tool took 4 minutes of compile time, the Rust crates seem to be very fine granular (like node.js vor example) and require much compile time. 204 crates needed to be compiled. I found that, using yay or another aur helper on arch linux, having a few rust utilities installed that have regular updates, significantly slows down the average system upgrade time. I tend to…

That's the nature of these spare time one (wo)man side projects: packaging a piece of software for a wide variety of distributions and platforms is tedious and boring, so unless there's a large community (or money) involved, you have to compile it from source. Of course, you can always package your favourite utility for your favourite distribution. I'm sure the author would be thrilled to endorse your package in the…

How is that musl based binary built ? I saw the repositories travis configuration and wasn't able to find anything relevant.

Re: What: A terminal tool to check what is taking up your bandwidth

#25

Post by gluegadget » Mon, Dec 30, 2019, 9:55 AM UTC

A bit unrelated but I wrote https://github.com/amir/hepccn to list TCP connections by domains rather than just IPs. It filters connections to port 443 and 8443, downloads the peer certificate and then extracts the subject name (pretty sure I learned this trick from an article on Julia Evans' website but can't find it now). I wanted to add more functionalities to it but I stumbled upon an issue and that's for when SNI is enabled. I guess there's no way for me to recover the hostname the client has sent at the start of the handshaking process without introducing MITM, right?

Re: What: A terminal tool to check what is taking up your bandwidth

#26

Post by lazyjones » Mon, Dec 30, 2019, 9:56 AM UTC

Bad naming..

  WHAT(1)                   BSD General Commands Manual                  WHAT(1)
  NAME
       what -- show what versions of object modules were used to construct a file

(MacOS ...)

Re: What: A terminal tool to check what is taking up your bandwidth

#27

Post by afinlayson » Mon, Dec 30, 2019, 9:57 AM UTC

afinlayson wrote: post #9

Why do I need cargo to install on mac? (It would be nice to have a link to install) Updated To install run: curl https://sh.rustup.rs -sSf | sh

Cargo isn't easily google-able ... I was hoping someone would link how to install it, instead of being sassy.

I figured it out.

It can be found here: https://doc.rust-lang.org/cargo/getting-started/installation...

You can install it easily by running this: curl https://sh.rustup.rs -sSf | sh

Re: What: A terminal tool to check what is taking up your bandwidth

#28

Post by uranusjr » Mon, Dec 30, 2019, 9:57 AM UTC

tiborsaas wrote: post #20

hnarn wrote: post #2

What are the main differences to something like nethogs or iftop?

Works on windows, osx too :)

The project page says it does not work on Windows.

Re: What: A terminal tool to check what is taking up your bandwidth

#29

Post by nsomaru » Mon, Dec 30, 2019, 10:02 AM UTC

avoro wrote: post #19

What can be a reason if on MacOS it does not capture traffic? I see empty panels. Tried to run with and without `sudo`.

Another poster did mention that a similarly named utility already exists on MacOS. Perhaps you’re invoking that instead?

Re: What: A terminal tool to check what is taking up your bandwidth

#30

Post by mobilemidget » Mon, Dec 30, 2019, 10:03 AM UTC

lazyjones wrote: post #26

Bad naming.. WHAT(1) BSD General Commands Manual WHAT(1) NAME what -- show what versions of object modules were used to construct a file (MacOS ...)

cargo install what (fails)

  Package `trust-dns-proto v0.18.0` does not have these features: `tokio-compat`

(MacOS 10.15.2)