This fact is especially true for sysadmins. Taking time to understand the basics of someone’s domain can go a long way toward improving relationships with other teams and shepherding faster resolutions to problems. Network admins, unable to control the servers and fatigued by the "guilty until proven innocent" attitude toward the network, would often blame the network endpoints. Sysadmins, lacking visibility into the network, would often blame the network for outages or strange issues. Have you ever used NetHogs or any other similar tool? How was your experience? Share your thoughts in the comments below.When I worked in a network-focused role, one of the biggest challenges was always bridging the gap between network and systems engineering. Plus, it’s an open source utility, which means you can study the way it works, and can even customize it the way you want. NetHogs is ideal for cases when you want to catch and kill the process that’s working unexpectedly by eating up a lot of bandwidth. And as always, “q” is for quitting the output. Similarly, you can press “s” and “r” to sort the output by data sent and received, respectively. ![]() Here is an example where traffic is displayed in MBs: ![]() For example, while the command is running, you can press the “m” key to change the units in which sent and received data is displayed – each time you press the key, the unit will cycle between kb/s, kb, b, and mb. The tool also provides some keyboard shortcuts which you can use to control the way the output is displayed. Note: you can use the -p command line option to sniff the traffic in promiscuous mode, although it is not recommended.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |