1. You can verify this from the output of netstat.

2. This will include a more detailed discussion of netstat.

3. You used netstat and drilled down to the packet level using tracing tools, such as iptrace and tcpdump.sentence dictionary

4. The command netstat -a list the connections (including port numbers); this can help you understand which connections have been made successfully.

5. Run netstat -Aan, where -A shows the address of any protocol control blocks associated with the sockets.

6. netstat, the equivalent of using vmstat or iostat for your memory reports, is a quick and dirty way of getting an overview of how your network is configured.

7. Listing 4 shows some of the options that netstat provides and the features they enable.

8. While running commands (such as netstat) can provide useful information, sometimes you need to drill down more to the packet level.

9. On successful login, the output of the netstat command will show a local port opened and listening for the port you specified (refer to Figure 5).

10. Using netstat, you can also monitor more detailed information about the packets themselves.

11. You need to understand the correct usage of netstat and how best to utilize it when monitoring your system.

12. There are actually so many different ways of using netstat that the best place to start is by looking at the man page and go from there.

13. You can look for signs of buffer congestion with netstat -s, which prints a list of network counters.

14. Part 1 of this series addressed some of the very basic flags, such as -in, that you typically use with netstat.

15. From a shell environment or a command window, issue the command netstat -a to list the TCP ports on which the system is listening.

16. Part 1 addressed some of the very basic flags, such as -in, that you typically use with netstat.

17. With RHEL5 networking, you also have the standard UNIX commands you should already be accustomed to, such as route, the netstat commands, and other utilities like ping and traceroute.

18. You can also get extended statistic information on all platforms by using the netstat tool.

19. Probably one of the most common commands you type in is netstat -in (see Listing 5).