| 1 |
Mick <michaelkintzios <at> gmail.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > Is there anything around to do this and not need a web server installed on |
| 5 |
> > the local machine? |
| 6 |
|
| 7 |
> Have a look at iftop, iptraf-ng and if you want more graphics ntop is worth |
| 8 |
> considering. |
| 9 |
|
| 10 |
> Beyond those tools you could look at snmp, rrdtool and if you want a full |
| 11 |
> blown monitoring tool with alerts and what not you could look at nagios, |
| 12 |
> cacti, munin, etc., but all these would require a webserver running. |
| 13 |
|
| 14 |
|
| 15 |
Here is an additional resource listing, including wireshark. These tools |
| 16 |
usually categorize traffic by port/protocol and not the specific |
| 17 |
process(es) but I'm sure if you dig deeply enough you'll find what |
| 18 |
you are looking for to characterize the traffic. |
| 19 |
|
| 20 |
hth, |
| 21 |
James |
| 22 |
|
| 23 |
|
| 24 |
[1] https://wiki.wireshark.org/Tools |
Archives