![]() ![]() It's simply not worth it, it's like going back in time 20 years. 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. I had to install 540MB of support files just to run "go get /gcla/termshark/cmd/termshark". But tshark also has a ton of options you can use, to do the same things as in Wireshark with the command line (for example, -f allow you to use capture filters. If I want a quick overview of a given machine I load up iftop, which isn't very thrilling on my desktop at the momentĪll 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. Usually I'm looking at RTP streams, so I run it through some perl to decode įor wider monitoring, at key points on the network I use ntop to see what's ![]() To see what they are, simply enter the command wireshark -h and the help information shown in Example 9.1, Help information available from Wireshark (or something similar) should be printed. Wireshark supports a large number of command line parameters. My first port of call tends to be tcpdump, with various filters and greps to pick out what I want. In this section we will look at starting it from the command line. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |