Linux Network Monitoring and Tuning: Difference between revisions

From Public wiki of Kevin P. Inscoe
Jump to navigation Jump to search
Line 18: Line 18:
*Analysing network errors and retransmissions
*Analysing network errors and retransmissions
*Device interrupts and loading
*Device interrupts and loading
*TCP slack and file transfers particularly FTP. Why it takes so long to transfer a file.
*TCP window size, maximum segment size (MSS) and global file transfers particularly FTP. Why it takes so long to transfer a file across a WAN or global connections.
*Bad network topology how to analyze. LAN vs WAN vs Internet (global) connections.
*Bad network topology how to analyze. LAN vs WAN vs Internet (global) connections.

Revision as of 16:01, 31 March 2017

Commands

nload - http://www.roland-riegel.de/nload/ and http://www.cyberciti.biz/networking/nload-linux-command-to-monitor-network-traffic-bandwidth-usage/

nmon - http://nmon.sourceforge.net/pmwiki.php

mtr - http://www.bitwizard.nl/mtr/

Socket Stats - ss command. http://www.cyberciti.biz/tips/linux-investigate-sockets-network-connections.html

Windows client - see http://www.netchain.com/netcps/

TBA

Things I have done research on and will post notes as soon as I can:

  • Buffers and connections and how they consume memory.
  • Analysing network errors and retransmissions
  • Device interrupts and loading
  • TCP window size, maximum segment size (MSS) and global file transfers particularly FTP. Why it takes so long to transfer a file across a WAN or global connections.
  • Bad network topology how to analyze. LAN vs WAN vs Internet (global) connections.