Information Technology News
Diagnose and manage your network for free with Linux and open source tools | Diagnose and manage your network for free with Linux and open source tools |
|
| by David M Williams | |
| Monday, 30 July 2007 | |
|
Page 2 of 4 traceroute
Featured Whitepaper
5 Best Practices for Smartphone Support
Don't be surprised, though, if periodically traceroute can't identify a system it passes through. The program depends on networks allowing low-level IP responses to be returned and these can sometimes be turned off. It's also important to understand that data won't always go the same way that traceroute's attempts figure out. This is because the whole basis of the Internet Protocol was to come up with a routing mechanism that could deliver data over a raft of different paths even if some nodes were lost due to conflict or other matters. Nevertheless, as a basic - and always available - network fault finding tool, traceroute is invaluable. You might also like to check out mtr - Matt's TraceRoute - which combines ping and traceroute together as well as giving graphical output. netstat
There are many other useful statistics to be gained from netstat; it can give extended information. It can show Ethernet statistics. It can give figures for each network interface. It can print a one-off list or it can continue running, refreshing values each second. Unfortunately, the way in which these options are invoked - as well as how the results are formatted - varies from implementation to implementation. It is worth becoming familiar with the man page for your local flavour of netstat but always keep it in mind as an essential tool that shows the paths your computer uses for data transfer as well as all the network activity running on your machine right now. |
| < Next story in category | Previous story in the category > |
|---|






