Scribd
Upload
85 views

Operating System Network Utilities

This document discusses several common network utilities used for troubleshooting and analysis on TCP/IP networks. It describes the ping, ifconfig, arp, traceroute, and netstat commands and provides examples of using each one to examine network connectivity and address translation tables. A lab experiment was conducted using these tools to monitor network interfaces, ping a neighbor, and view active connections, but some portions could not be completed due to the isolated lab network having no internet connection.

Uploaded by

Avi Narine
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
85 views

Operating System Network Utilities

This document discusses several common network utilities used for troubleshooting and analysis on TCP/IP networks. It describes the ping, ifconfig, arp, traceroute, and netstat commands and provides examples of using each one to examine network connectivity and address translation tables. A lab experiment was conducted using these tools to monitor network interfaces, ping a neighbor, and view active connections, but some portions could not be completed due to the isolated lab network having no internet connection.

Uploaded by

Avi Narine
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

TITLE:

Operating Systems Network Utilities

Aim: To become familiarized with the basic troubleshooting and analysis tools that are available on most systems that use TCP/IP. Definitions: Ping- Packet Internet Groper, uses ICMP to verify network connectivity and correct operation of the protocol stack. Ifconfig- Used to set or display variables for each network interface associated with a system. Arp- Used to set or display entries in the address translation table. Traceroute- Similar to the ping command in that it uses ICMP to identify routers in an end network connection. Netstat- Presents information about network connections, routing tables, interface statistics and other details on the host system. Procedures: Ifconfig Using the ifconfig command to record details about the Ethernet interface:
LOOPBAC K HARDWARE ADDRESS INTERNET ADDRESS NETWORK MASK 127.0.0.1 255.0.0.0 ETHERNET 0 00:10:DC:5B:66: 18 192.168.100.11 255.255.255.0

ARP The arp command (arp a or arp an) was used to examine the address translation cache on the system we were using. [root@localhost root]# arp -a ? (192.168.100.14) at 00:10:DC:58:83:D2 [ether] PERM on eth0 ? (192.168.100.12) at 00:10:DC:5B:A2:A4 [ether] PERM on eth0 ? (192.168.100.13) at <incomplete> on eth0 ? (192.168.100.1) at <incomplete> on eth0

The ping command was used to ping a neighbors computer and then the address translation cache was reexamined. [root@localhost root]# ping 192.168.100.14

PING 192.168.100.14 (192.168.100.14) 56(84) bytes of data. 64 bytes from 192.168.100.14: icmp_seq=1 ttl=64 time=0.219 ms 64 bytes from 192.168.100.14: icmp_seq=2 ttl=64 time=0.208 ms 64 bytes from 192.168.100.14: icmp_seq=3 ttl=64 time=0.197 ms 64 bytes from 192.168.100.14: icmp_seq=4 ttl=64 time=0.208 ms 64 bytes from 192.168.100.14: icmp_seq=5 ttl=64 time=0.212 ms 64 bytes from 192.168.100.14: icmp_seq=6 ttl=64 time=0.173 ms --- 192.168.100.14 ping statistics --6 packets transmitted, 6 received, 0% packet loss, time 5009ms rtt min/avg/max/mdev = 0.173/0.202/0.219/0.023 ms The arp command (arp d) was used to delete the neighbors address translation entry and then the arp command (arp s) was used to replsce the entry with a different Ethernet address. After this was done the neighbors pc was pinged. [root@localhost root]# arp -d 192.168.100.14 [root@localhost root]# arp -s 192.168.100.14 00:10:DC:58:24:D2 [root@localhost root]# ping 192.168.100.14 PING 192.168.100.14 (192.168.100.14) 56(84) bytes of data. --- 192.168.100.14 ping statistics --4 packets transmitted, 0 received, 100% packet loss, time 2403ms PING Remote Host A lab workstation Your default gateway Thunder.ict.sait.ab.ca Webct.sait.ab.ca www.sait.ab.ca RTT 0.196 -

In this portion of the lab, the RTT for the blank fields were not filled out because the lab did not have an Internet connection. TRACEROUTE In this portion of the lab, the traceroute was not completed because the lab did not have an Internet connection.

NETSTAT Using the telnet command: Your Machine 192.168.100.11 2411 192.168.100.14 33980 Partners Machine 192.168.100.14 33980 192.168.100.11 2411

Source IP Source Port Destination IP Destination Port Using FTP:

Source IP Source Port Destination IP Destination Port Using SFTP:

Your Machine 192.168.100.11 8021 192.168.100.14 34116

Partners Machine 192.168.100.14 34116 192.168.100.11 41327

Source IP Source Port Destination IP Destination Port

Your Machine 192.168.100.11 445 192.168.100.14 34116

Partners Machine 192.168.100.14 34116 192.168.100.11 445

Discussion: This lab was a little introduction to the greater understanding of how the utilities operate. They just gave us a basic understanding of their operation.

Conclusion: The lab was done successfully but the limiting factor in some parts of the lab was that there was not an internet connection available to do so. Another limiting factor was the lab itself having its network in a disorderly state.

You might also like