2 ms·

My first port of call tends to be tcpdump, with various filters and greps to pick out what I want. Usually I'm looking at RTP streams [0], so I run it through s

My first port of call tends to be tcpdump, with various filters and greps to pick out what I want. Usually I'm looking at RTP streams [0], so I run it through some perl to decode [1] For wider monitoring, at key points on the network I use ntop [2] to see what's If I want a quick overview of a given machine I load up iftop [3], which isn't very thrilling on my desktop at the moment [0] https://i.imgur.com/O9ekuPt.png https://i.imgur.com/O9ekuPt.png [1] https://i.imgur.com/x9l0UNd.png https://i.imgur.com/x9l0UNd.png [2] https://i.imgur.com/gFXAxwa.png https://i.imgur.com/gFXAxwa.png [3] https://i.imgur.com/vmpgR6i.png https://i.imgur.com/vmpgR6i.png All of these are trivial to install (except for the RTP perl script which I have as a custom apt-gettable package) and don't require non-standard interpreters and package managers. Nethertheless I went to get this. I had to install 540MB of support files just to run "go get github.com/gcla/termshark/cmd/termshark". Still it compliles. Then I run it, and it shows bugger all, I suspect I need to find and install more libraries (tcell, gowid), which themselves require massive downloads. It's simply not worth it, it's like going back in time 20 years.

gcla 8y ago
hi isostatic - sorry for the trouble :( I had hoped that compiling it would be quick and reliable. By default termshark will be installed in ~/go/bin/ - though it sounds like you have it compiled, it's just not running. Send me a message if you like and I'll see if I can get it working for you. There are also pre-compiled binaries at https://github.com/gcla/termshark/releases https://github.com/gcla/termshark/releases
- isostatic 8y ago
  As an old fart I expect to type "./configure; make", however it did seem to compile. It runs, just doesn't look like it's reading anything from "sudo ./termshark -i eno1 icmp". Works fine when reading a pcap file, works fine when launching from a root session (rather than via sudo)
kchr 8y ago
How is that different from compiling other software with build dependencies? I mean, if you consider libc etc most applications have quite a large tree of build deps if you need to download _all_ libraries from scratch - it's just that in most cases you already have those deps. Next time you need to build a golang project you most likely won't have to download all of those libs again, unless you remove them for some reason.

gcla 8y ago

hi isostatic - sorry for the trouble :( I had hoped that compiling it would be quick and reliable. By default termshark will be installed in ~/go/bin/ - though it sounds like you have it compiled, it's just not running. Send me a message if you like and I'll see if I can get it working for you. There are also pre-compiled binaries at https://github.com/gcla/termshark/releases https://github.com/gcla/termshark/releases

isostatic 8y ago
As an old fart I expect to type "./configure; make", however it did seem to compile. It runs, just doesn't look like it's reading anything from "sudo ./termshark -i eno1 icmp". Works fine when reading a pcap file, works fine when launching from a root session (rather than via sudo)

kchr 8y ago

How is that different from compiling other software with build dependencies? I mean, if you consider libc etc most applications have quite a large tree of build deps if you need to download _all_ libraries from scratch - it's just that in most cases you already have those deps. Next time you need to build a golang project you most likely won't have to download all of those libs again, unless you remove them for some reason.