This is a list of notable port numbers used by protocols of the transport layer of the Internet protocol suite for the establishment of host-to-host connectivity.
Originally, port numbers were used by the Network Control Program (NCP) in the ARPANET for which two ports were required for half-duplex transmission.
The ARP protocol was defined in RFC 826 , written by David Plummer in 1982.
The arp protocol is a broadcast protocol: it receives a destination IP address and sends out a broadcast request for all machines to see.
(for non-text base protocols, like DNS) Smart Sniff provides 3 methods for capturing TCP/IP packets : Win Pcap Capture Driver: Allows you to capture TCP/IP packets on all Windows operating systems.
(Windows 98/ME/NT/2000/XP/2003/Vista) In order to use it, you have to download and install Win Pcap Capture Driver from this Web site.
If the final destination is on a different network, an address resolution might be required on each network that the message traverses on the path to its final destination.
This article lists port numbers and their associated protocols that have experienced significant uptake.
The Stream Control Transmission Protocol (SCTP) and the Datagram Congestion Control Protocol (DCCP) also use port numbers.
They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist.
Later, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) needed only one port for full-duplex, bidirectional traffic.
The even-numbered ports were not used, and this resulted in some even numbers in the well-known port number range being unassigned.