Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

41–50 of 190 posts

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

#41

Post by tialaramex »

gluegadget wrote: post #25

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…

You won't be able to recover it after the fact, but the SNI is cleartext on the wire as part of ClientHello even in TLS 1.3. Work to encrypt this is an ongoing effort (called eSNI).

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

#42

Post by pmontra »

I find the --raw output more useful than the interactive one. it scrolls away but I have time to read what's going on. The other one just disappears and is replaced by something else, which could be ok except sometimes there are seconds of useless black screen when nothing is going on. I suggest to never have blank screens. A suggestion for the raw output: add a timestamp at the beginning of the line. Probably HHMMSS is enough but YYYYmmdd would be handy for logging in background.

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

#43

Post by bitlevel »

xorcist wrote: post #40
Symbiote wrote: post #32

Earlier quoted context omitted.

'whence' would be more specific – it's archaic in English, it means 'from where' – although it's used within the ksh shell.

zsh also implements whence

Perhaps 'whip' for 'what internet protocol'?

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

#44

Post by pmontra »

bicolao wrote: post #31
jxf wrote: post #7

Earlier quoted context omitted.

They are similar but they answer different questions. By default, iftop will tell you "this network interface on your machine is talking a lot to ycombinator.com". But you don't necessarily know which processes are doing the most talking collectively. This will tell you "Firefox process 4567 is talking a lot ycombinator.com" and you'll know whether 4567 is also one of the chattiest talkers right now.

> This will tell you "Firefox process 4567 is talking a lot ycombinator.com" and you'll know whether 4567 is also one of the chattiest talkers right now. But that's what nethogs does.

nethogs doesn't have the raw output mode. That could be useful. I'd take nethogs' real time display and what's raw output.

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

#47

Post by mrtksn »

aspaceman wrote: post #39
afinlayson wrote: post #27

Earlier quoted context omitted.

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

Very first result for "cargo tool programming" https://binx.io/blog/2018/11/27/learning-cargo/ You're getting snark because your own snarky comment is the equivalent of saying "Why do I need Make to run it on the MacOS?" If you had asked instead, "What is cargo, and how do I install it?" you would get more helpful responses. Snark is met with snark.

And how people are supposed to know that it is a programming tool? I assumed that it is yet another package manager and googling about cargo brings results about logistics.

It took me a few tries before figuring it out. What worked was "Install cargo MacOS" and it was hard to tell if the results are not a scam to make me install some spyware.

Post reply on HN