tag:blogger.com,1999:blog-23643004100273388742009-07-14T08:01:34.778-07:00handbook,.fakrule bromonoreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2364300410027338874.post-38238467045866231402009-07-14T07:41:00.001-07:002009-07-14T07:43:01.622-07:00Network Security Technologies and Protocols<blockquote><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Description</b><a name="Network security"></a> Network security covers such issues as network communication privacy, information confidentiality and integrity over network, controlled access to restricted network domains and sensitive information, and using the public network such as Internet for private communications. To address these issues, various network and information security technologies have been developed by various organizations and technology vendors. Here is a summary of the technologies: </p><p style="text-align: justify;" class="docText"><a name="is a"></a>AAA: Authorization, Authentication and Accounting is a technology for intelligently controlling access to network resources, enforcing policies, auditing usage, and providing the information necessary to bill for services. Authentication provides a way of identifying a user, typically by having the user enter a valid user name and valid password before access is granted. The authorization process determines whether the user has the authority to access certain information or some network sub-domains. Accounting measures the resources a user consumes while using the network, which includes the amount of system time or the amount of data a user has sent and/or received during a session, which could be used for authorization control, billing, trend analysis, resource utilization, and capacity planning activities. A dedicated AAA server or a program that performs these functions often provides authentication, authorization, and accounting services. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="is a"></a>VPN: Virtual Private Network is a technology allowing private communications by business and individuals, such as remote access to a corporate network or using a public telecommunication infrastructure, such as the Internet. A virtual private network can also be a specially configured network over the public network infrastructure that is only used by one organization. Various network-tunneling technologies such as L2TP have been developed to reach this goal. Using encryption technologies such as IPsec could further enhance information privacy over network and virtual private networks. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="a software"></a>Firewall: Firewall is a software program or hardware device that filters the information coming through the Internet connection into a private network or computer system. Firewalls use one or more of three methods to control traffic flowing in and out the network: </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"> </p><ul style="text-align: justify;"><li> <p class="docList"><a name="are analyzed"></a>Packet filtering - Packets are analyzed against a set of filters. Packets that make it through the filters are sent to the requesting system and all others are discarded. </p> </li><li> <p class="docList"><a name="firewall and"></a>Proxy service - Information from the Internet is retrieved by the firewall and then sent to the requesting system and vice versa. </p> </li><li> <p class="docList"><a name="packets passing"></a>Stateful inspection - compares certain key parts of packets passing through with a database of trusted information. Outgoing information from inside the firewall is monitored for specific defining characteristics, and incoming information is then compared with these characteristics. If the comparison yields a reasonable match, the information is allowed through. Otherwise it is discarded. </p></li></ul> <p class="docText"><b>Protocols</b><a name="AAA and"></a> The key protocols for AAA and VPN: </p><p class="docText"><a name="par03tb01"></a> </p><p> <table style="width: 611px; height: 606px;" class="allBorders" border="1" cellspacing="0"> <colgroup align="middle" span="2"> <col width="250"> <col width="250"></colgroup> <thead></thead> <tbody> <tr> <td class="docTableCell" rowspan="4" align="middle">Authentication Authorization Accounting</td> <td class="docTableCell" align="middle">Kerberos: Network Authentication Protocol</td></tr> <tr> <td class="docTableCell" align="middle">RADIUS: Remote Authentication Dial In User Service</td></tr> <tr> <td class="docTableCell" align="middle">SSH: Secure Shell Protocol</td></tr> <tr> <td class="docTableCell" align="middle">TACACS: Terminal Access Controller Access Control Protocol (and TACACS+)</td></tr> <tr> <td class="docTableCell" rowspan="3" align="middle">Tunneling</td> <td class="docTableCell" align="middle">L2F: Level 2 Forwarding protocol</td></tr> <tr> <td class="docTableCell" align="middle">L2TP: Layer 2 Tunneling Protocol</td></tr> <tr> <td class="docTableCell" align="middle">PPTP: Point to Point Tunneling Protocol</td></tr> <tr> <td class="docTableCell" rowspan="8" align="middle">Secured Routing</td> <td class="docTableCell" align="middle">DiffServ: Differentiated Service</td></tr> <tr> <td class="docTableCell" align="middle">GRE: Generic Routing Encapsulation</td></tr> <tr> <td class="docTableCell" align="middle">IPsec: Security Architecture for IP network</td></tr> <tr> <td class="docTableCell" align="middle">IPsec AH: IPsec Authentication Header</td></tr> <tr> <td class="docTableCell" align="middle">IPsec ESP: IPsecEncapsulating Security Payload</td></tr> <tr> <td class="docTableCell" align="middle">IPsec IKE: Internet Key Exchange Protocol</td></tr> <tr> <td class="docTableCell" align="middle">IPsec ISAKMP: Internet Security Association and Key Management Protocol</td></tr> <tr> <td class="docTableCell" align="middle">TLS: Transport Layer Security Protocol</td></tr> <tr> <td class="docTableCell" align="middle">Others</td> <td class="docTableCell" align="middle">Socks: Protocol for sessions traversal across firewall securely</td></tr></tbody></table></p><br /> <p class="docText"><b>Reference</b> </p><pre><a class="docLink" href="http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/security.htm" target="_blank">http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/security.htm</a><br />Securities Technologies<br /></pre> </blockquote> <p><br /></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-3823846704586623140?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0tag:blogger.com,1999:blog-2364300410027338874.post-40605818248266538222009-07-14T07:37:00.002-07:002009-07-14T07:39:59.609-07:00Voice over IP and VOIP Protocols<blockquote><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Description</b><a name="Voice over"></a> Voice over IP (VOIP) uses the Internet Protocol (IP) to transmit voice as packets over an IP network. Using VOIP protocols, voice communications can be achieved on any IP network regardless whether it is Internet, Intranet or Local Area Networks (LAN). In a VOIP enabled network, the voice signal is digitized, compressed and converted to IP packets and then transmitted over the IP network. VOIP signaling protocols are used to set up and tear down calls, carry information required to locate users and negotiate capabilities. The key benefits of Internet telephony (Voice over IP) are the very low cost, the integration of data, voice and video on one network, the new services created on the converged network and simplified management of end user and terminals. </p><p style="text-align: justify;" class="docText"><a name="few VOIP"></a>There are a few VOIP protocol stacks which are derived by various standard bodies and vendors, namely H.323, SIP, MEGACO and MGCP. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="was originally"></a>H.323 is the ITU-T's standard, which was originally developed for multimedia conferencing on LANs, but was later extended to cover Voice over IP. The standard encompasses both point to point communications and multipoint conferences. H.323 defines four logical components: Terminals, Gateways, Gatekeepers and Multipoint Control Units (MCUs). Terminals, gateways and MCUs are known as endpoints. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="Protocol"></a>Session Initiation Protocol (SIP) is the IETF's standard for establishing VOIP connections. SIP is an application layer control protocol for creating, modifying and terminating sessions with one or more participants. The architecture of SIP is similar to that of HTTP (client-server protocol). Requests are generated by the client and sent to the server. The server processes the requests and then sends a response to the client. A request and the responses for that request make a transaction. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="Protocol"></a>Media Gateway Control Protocol (MGCP), an IETF standard based on Cisco and Telcordia proposals, defines communication between call control elements (Call Agents or Media Gateway) and telephony gateways. MGCP is a control protocol, allowing a central coordinator to monitor events in IP phones and gateways and instruct them to send media to specific addresses. In the MGCP architecture, the call control intelligence is located outside the gateways and is handled by the call control elements (the Call Agent). Also, the call control elements (Call Agents) will synchronize with each other to send coherent commands to the gateways under their control. CableLab has adopted the MGCP for its PacketCable embbed clients in VOIP applications and the resulted protocol is called Network Based Signaling Protocol (NCS). </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="efforts of"></a>The Media Gateway Control Protocol (Megaco) is a result of joint efforts of the IETF and the ITU-T (ITU-T Recommendation H.248). Megaco/H.248 is a protocol for the control of elements in a physically decomposed multimedia gateway, which enables separation of call control from media conversion. Megaco/H.248 addresses the relationship between the Media Gateway (MG), which converts circuit-switched voice to packet-based traffic, and the Media Gateway Controller, which dictates the service logic of that traffic. Megaco/H.248 instructs an MG to connect streams coming from outside a packet or cell data network onto a packet or cell stream such as the Real-Time Transport Protocol (RTP). Megaco/H.248 is essentially quite similar to MGCP from an architectural standpoint and the controller-to-gateway relationship, but Megaco/H.248 supports a broader range of networks. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="the circuit"></a>The SS7/C7 is the traditional signaling protocol for the circuit switched voice networks. To integrate the SS7/C7 network with the IP network, a group of protocols are defined, namely SIGTRAN (Signaling Transpor protocol). The key transport protocol in the SIGTRAN stack, the Stream Control Transmission Protocol (SCTP), has been applied in a much broader base after its creation. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="the VOIP"></a>In the past few years, the VOIP industry has been working on addressing the following key issues: </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="does not"></a>Quality of voice -- As IP was designed for carrying data, it does not provide real time guarantees but only provides best effort service. For voice communications over IP to become acceptable to users, the packet delay and getter needs to be less than a threshold value. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="Interoperability"></a>Interoperability -- In a public network environment, products from different vendors need to operate with each other for Voice over IP to become common among users. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="and tunneling"></a>Security -- Encryption (such as SSL) and tunneling (L2TP) technologies have been developed to protect VOIP signaling and bear traffic. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="Switched Telephone"></a>Integration with Public Switched Telephone Network(PSTN) -- While Internet telephony is being introduced, it will need to work in conjunction with PSTN in the foreseeable future. Gateway technologies are being developed to bridge the two networks. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="systems need"></a>Scalability -- VOIP systems need to be flexible enough to grow to the large user market for both private and public services. Many network management and user management technologies and products are being developed to address the issue. </p> <p class="docText"><b>Key VOIP Protocols</b> <a name="par04tb01"></a> </p><p> <table style="width: 613px; height: 943px;" class="allBorders" border="1" cellspacing="0"> <colgroup align="left" span="2"> <col width="250"> <col width="250"></colgroup> <thead></thead> <tbody> <tr align="left"> <td class="docTableCell" colspan="2"> Signaling</td></tr> <tr> <td style="text-align: center;" class="docTableCell" rowspan="5">ITU-T H.323</td> <td class="docTableCell" align="left">H.323: Packet-based multimedia communications (VoIP) architecture</td></tr> <tr> <td class="docTableCell" align="left"><a name="RAS in"></a>H.225: Call Signaling and RAS in H.323 VOIP Architecture</td></tr> <tr> <td class="docTableCell" align="left">H.235: Security for H.323 based systems and communications</td></tr> <tr> <td class="docTableCell" align="left">H.245: Control Protocol for Multimedia Communication</td></tr> <tr> <td class="docTableCell" align="left">T.120: Multipoint Data Conferencing Protocol Suite</td></tr> <tr> <td style="text-align: center;" class="docTableCell" rowspan="6">IETF</td> <td class="docTableCell" align="left">Megaco / H.248: Media Gateway Control protocol</td></tr> <tr> <td class="docTableCell" align="left">MGCP: Media Gateway Control Protocol</td></tr> <tr> <td class="docTableCell" align="left">RTSP: Real Time Streaming Protocol</td></tr> <tr> <td class="docTableCell" align="left">SIP: Session Initiation Protocol</td></tr> <tr> <td class="docTableCell" align="left">SDP: Session Description Protocol</td></tr> <tr> <td class="docTableCell" align="left">SAP: Session Announcement Protocol</td></tr> <tr> <td style="text-align: center;" class="docTableCell">CableLab</td> <td class="docTableCell" align="left">NCS: Netowrk-based Call Signaling Protocol</td></tr> <tr> <td style="text-align: center;" class="docTableCell">Cisco Skinny</td> <td class="docTableCell" align="left">SCCP: Skinny Client Control Protocol</td></tr> <tr> <td style="text-align: center;" class="docTableCell" rowspan="6">Media/CODEC</td> <td class="docTableCell" align="left">G.7xx: Audio (Voice) Compression Protocols (G.711, G.721, G.722, G.723, G.726, G.727. G.728, G.729)</td></tr> <tr> <td class="docTableCell" align="left">H.261: Video CODEC for Low Quality Videoconferencing</td></tr> <tr> <td class="docTableCell" align="left">H.263: Video CODEC for Medium Quality Videoconferencing</td></tr> <tr> <td class="docTableCell" align="left">H.264 / MPEG-4: Video CODEC for High Quality Video Streaming</td></tr> <tr> <td class="docTableCell" align="left">Video CODEC for Medium Quality VideoconferencingRTP: Real Time Transport Protocol</td></tr> <tr> <td class="docTableCell" align="left">RTCP: RTP Control Protocol</td></tr> <tr> <td style="text-align: center;" class="docTableCell" rowspan="4">Others</td> <td class="docTableCell" align="left">COPS: Common Open Policy Service</td></tr> <tr> <td class="docTableCell" align="left">SIGTRAN: Signaling Transport protocol stack for SS7/C7 over IP</td></tr> <tr> <td class="docTableCell" align="left">SCTP: Stream Control Transmission Protocol</td></tr> <tr> <td class="docTableCell" align="left">TRIP: Telephony Routing Over IP</td></tr></tbody></table></p><br /> <p class="docText"><b>Sponsor Source</b> VOIP protocols are defined by IETF, ITU-T and some vendors. </p> <p class="docText"><b>Reference</b> </p><pre><a class="docLink" href="http://www.cis.ohio-state.edu/%7Ejain/refs/ref_voip.htm" target="_blank">http://www.cis.ohio-state.edu/~jain/refs/ref_voip.htm</a><br />Voice Over IP and IP Telephony References<br /></pre> </blockquote> <p><br /></p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-4060581824826653822?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0tag:blogger.com,1999:blog-2364300410027338874.post-90493440329977192602009-07-14T07:32:00.001-07:002009-07-14T07:34:26.452-07:00Cisco Protocols<blockquote><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Description</b><a name="Cisco Systems"></a> Cisco Systems plays an active role in the IETF committees to bring Cisco technology initiatives into the standards track. At the same time, Cisco created many proprietary protocols, which are mostly included in the IOS, the operating system of Cisco products. In this book, we have selected the most frequently used Cisco protocols to introduce. </p><pre>CDP: Cisco Discovery Protocol<br />CGMP: Cisco Group Management Protocol<br />DISL: Dynamic Inter-Switch Link Protocol<br />DTP: Cisco Dynamic Trunking Protocol<br />EIGRP: Enhanced Interior Gateway Routing Protocol<br />HSRP: Hot Standby Router Protocol<br />IGRP: Interior Gateway Routing Protocol<br />ISL: Cisco Inter-Switch Link Protocol<br />NetFlow: Cisco traffic mamagement protocol<br />RGMP: Cisco Router Port Group Management Protocol<br />TACACS and TACACS+: Terminal Access Controller Access Control Protocol<br />VTP: Cisco VLAN Trunking Protocol<br />XOT: Cisco X.25 Over TCP Protocol<br /></pre> </blockquote><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-9049344032997719260?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0tag:blogger.com,1999:blog-2364300410027338874.post-38122977844388345962009-07-14T07:14:00.001-07:002009-07-14T07:16:39.376-07:00Wide Area Network and WAN Protocols<p style="text-align: justify;" class="docText"><b>Description</b><a name="A Wide"></a> A Wide Area Network (WAN) is a computer network covering multiple distance areas, which may spread across the entire world. WANs often connect multiple smaller networks, such as local area networks (LANs) or metro area networks (MANs). The world's most popular WAN is the Internet. Some segments of the Internet are also WANs in themselves. A wide area network may be privately owned or rented from a service provider, but the term usually connotes the inclusion of public (shared user) networks. </p><p style="text-align: justify;" class="docText"><a name="network"></a>A virtual private network (VPN) riding on the public switched data network (PSDN) is often used by organizations for their private and secured communications. VPN uses encryption and other techniques to make it appear that the organisation has a dedicated network while making use of the shared infrastructure of the WAN. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="different networking"></a>WANs generally utilize different networking technologies and equipment than do LANs. Key technologies often found in WANs include SONET, Frame Relay, X.25, ATM, and PPP. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="and protocols"></a>WAN technologies and protocols are mostly data link layer (layer 2) protocols which are defined by many organizations over time. The key organizations in this space are IETF for PPP, ITU-T for ATM, Frame Relay, ISO for X.25 and SONET. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Key Protocols</b><a name="protocols are"></a> The key WAN protocols are listed as follows:</p><p style="text-align: justify;" class="docText"> </p><p><table style="width: 650px; height: 1325px;" class="allBorders" border="1" cellspacing="0"> <caption> <h5 class="docTableTitle">Table 0501. </h5></caption> <colgroup align="middle" span="2"> <col width="250"> <col width="250"></colgroup> <thead> <tr> <th class="docTableCell thead" style="text-align: center;" scope="col" align="middle">WAN</th> <th class="docTableCell thead" style="text-align: center;" scope="col" align="middle">Wide Area Network</th></tr></thead> <tbody> <tr> <td class="docTableCell" rowspan="9" align="middle">ATM</td> <td class="docTableCell" align="middle">ATM: Asynchronous Transfer Mode Reference Model</td></tr> <tr> <td class="docTableCell" align="middle">ATM Layer</td></tr> <tr> <td class="docTableCell" align="middle">AAL: ATM Adaptation Layer Type 0-5 reserved for variable bit rate video transfer.</td></tr> <tr> <td class="docTableCell" align="middle">ATM UNI: ATM Signaling User-to-Network Interface</td></tr> <tr> <td class="docTableCell" align="middle">LANE-NNI: LAN Emulation - Network to Network Interface</td></tr> <tr> <td class="docTableCell" align="middle">LANE-UNI: LAN Emulation - User to Network Interface</td></tr> <tr> <td class="docTableCell" align="middle">MPOA: Multi Protocol Over ATM</td></tr> <tr> <td class="docTableCell" align="middle">PNNI: Private Network-to-Network Interface</td></tr> <tr> <td class="docTableCell" align="middle">Q.2931: ATM Signalling User Interface</td></tr> <tr> <td class="docTableCell" rowspan="2" align="middle">SONET/SDH</td> <td class="docTableCell" align="middle">Synchronous Optical Network and Synchronous Digital Hierarchy</td></tr> <tr> <td class="docTableCell" align="middle">EoS: Ethernet over SONET/SDH</td></tr> <tr> <td class="docTableCell" rowspan="6" align="middle">Broadband Access</td> <td class="docTableCell" align="middle">DOCSIS: Data Over Cable Service Interface Specification</td></tr> <tr> <td class="docTableCell" align="middle">BISDN: Broadband Integrade Service Digital Network</td></tr> <tr> <td class="docTableCell" align="middle">ISDN: Integrated Services Digital Network</td></tr> <tr> <td class="docTableCell" align="middle">Q.931: ISDN network layer interface protocol</td></tr> <tr> <td class="docTableCell" align="middle">LAPD: ISDN Link Access Protocol Channel D (Q.921)</td></tr> <tr> <td class="docTableCell" align="middle">xDSL: Digital Subscriber Line Technologies (DSL, IDSL, ADSL, HDSL, SDSL, VDSL, G.Lite)</td></tr> <tr> <td class="docTableCell" rowspan="13" align="middle">PPP</td> <td class="docTableCell" align="middle">PPP: Point-to-Point Protocols</td></tr> <tr> <td class="docTableCell" align="middle">BAP: PPP Bandwidth Allocation Protocol</td></tr> <tr> <td class="docTableCell" align="middle">BACP: PPP Bandwidth Allocation Control Protocol</td></tr> <tr> <td class="docTableCell" align="middle">BCP: PPP Bridging Control Protocol</td></tr> <tr> <td class="docTableCell" align="middle">CHAP: Challenge Handshake Authentication Protocol</td></tr> <tr> <td class="docTableCell" align="middle">EAP: PPP Extensible Authentication Protocol</td></tr> <tr> <td class="docTableCell" align="middle">LCP: PPP Link Control Protocol</td></tr> <tr> <td class="docTableCell" align="middle">MultiPPP: MultiLink PPP (MP)</td></tr> <tr> <td class="docTableCell" align="middle">NCP: PPP Network Control Protocol</td></tr> <tr> <td class="docTableCell" align="middle">PAP: Password Authentication Protocol</td></tr> <tr> <td class="docTableCell" align="middle">PPPoE: PPP over Ethernet</td></tr> <tr> <td class="docTableCell" align="middle">PPPoA: PPP over ATM AAL5</td></tr> <tr> <td class="docTableCell" align="middle">PoS: Packet Over SONET/SDH</td></tr> <tr> <td class="docTableCell" rowspan="3" align="middle">X.25</td> <td class="docTableCell" align="middle">HDLC: High Level Data Link Control protocol</td></tr> <tr> <td class="docTableCell" align="middle">LAPB: Link Access Procedure Balanced for x.25</td></tr> <tr> <td class="docTableCell" align="middle">X.25: ITU-T WAN communication protocol</td></tr> <tr> <td class="docTableCell" rowspan="2" align="middle">Frame Relay</td> <td class="docTableCell" align="middle">Frame Relay: WAN protocol for internetworking at layer 2</td></tr> <tr> <td class="docTableCell" align="middle">LAPF: Link Access Procedure/Protocol (ITU Q.922)</td></tr> <tr> <td class="docTableFooter" align="middle">Other</td> <td class="docTableFooter" align="middle">IBM SDLC: Synchronous Data Link Control protocol</td></tr></tbody></table></p><br /> <p class="docText"><b>Related Protocols</b> LAN, MAN, TCP/IP </p><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-3812297784438834596?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0tag:blogger.com,1999:blog-2364300410027338874.post-88784978282150719732009-07-14T07:09:00.000-07:002009-07-14T07:12:58.957-07:00TCP/IP Protocols<div style="text-align: justify;"><div style="text-align: justify;"><b></b></div><div style="text-align: justify;"><div style="text-align: justify;"><div style="text-align: justify;"><p style="text-align: justify;" class="docText"><a name="The TCP"></a>The TCP/IP protocol suite establishes the technical foundation of the Internet. Development of the TCP/IP started as DOD projects. Now, most protocols in the suite are developed by the Internet Engineering Task Force (IETF) under the Internet Architecture Board (IAB), an organization initially sponsored by the US government and now an open and autonomous organization. The IAB provides the coordination for the R&D underlying the TCP/IP protocols and guides the evolution of the Internet. The TCP/IP protocols are well documented in the Request For Comments (RFC), which are drafted, discussed, circulated and approved by the IETF committees. All documents are open and free and can be found online in the IETF site listed in the reference. </p><div> </div><p style="text-align: justify;" class="docText"><a name="exactly match"></a>TCP/IP architecture does not exactly match the OSI model. Unfortunately, there is no universal agreement regarding how to describe TCP/IP with a layered model. It is generally agreed that TCP/IP has fewer levels (from three to five layers) than the seven layers of the OSI model. In this document, we force TCP/IP protocols into the OSI 7 layers structure for comparison purpose. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><a name="are addressing"></a>The TCP/IP suite's core functions are addressing and routing (IP/IPv6 in the networking layer) and transportation control (TCP, UDP in the transport layer). </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>IP - Internet Protocol</b><a name="network components"></a> Addressing of network components is a critical issue for information routing and transmission in network communications. Each technology has its own convention for transmitting messages between two machines within the same network. On a LAN, messages are sent between machines by supplying the six bytes unique identifier (the "MAC" address). In an SNA network, every machine has Logical Units with their own network addresses. DECNET, AppleTalk, and Novell IPX all have a scheme for assigning numbers to each local network and to each workstation attached to the network. </p><p style="text-align: justify;" class="docText"><a name="these local"></a>On top of these local or vendor specific network addresses, IP assigns a unique number to every network device in the world, which is called an IP address. This IP address is a four-byte value in IPv4 that, by convention, is expressed by converting each byte into a decimal number (0 to 255) and separating the bytes with a period. In IPv6, the IP address has been increased to 16 bytes. Details of the IP and IPv6 protocols are presented in separate documents. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>TCP - Transmission Control Protocol</b><a name="to applications"></a> TCP provides a reliable stream delivery and virtual connection service to applications through the use of sequenced acknowledgment with retransmission of packets when necessary. TCP provides stream data transfer, transportation reliability, efficient flow control, full-duplex operation, and multiplexing. Check the TCP section for more details. In the follwoing TCP/IP protocol stack table, we list all the protocols according to their functions in mapping to the OSI 7 layers network communication reference model. </p><p style="text-align: justify;" class="docText"><a name="model closely"></a>However, the TCP/IP architecture does not follow the OSI model closely, for example, most TCP/IP applications directly run on top of the transport layer protocols, TCP and UDP, without the presentation and session layers in between. </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText">TCP/IP Protocol Stack </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Application Layer</b> </p><div style="text-align: justify;"><pre class="pre">BOOTP: Bootstrap Protocol<br />DCAP: Data Link Switching Client Access Protocol<br />DHCP: Dynamic Host Configuration Protocol<br />DNS: Domain Name Systems<br />FTP: File Transfer Protocol<br />Finger: User Information Protocol<br />HTTP: Hypertext Transfer Protocol<br />S-HTTP: Secure Hypertext Transfer Protocol (S-HTTP)<br />IMAP & IMAP4: Internet Message Access Protocol<br />IPDC: IP Device Control<br />IRCP (IRC): Internet Relay Chat Protocol<br />LDAP: Lightweighted Directory Access Protocol<br />MIME (S-MIME): Multipurpose Internet Mail Extensions (Secure MIME)<br />NAT: Network Address Translation<br />NNTP: Network News Transfer Protocol<br />NTP: Network Time Protocol<br />POP & POP3: Post Office Protocol (version 3)<br />rlogin: Remote Login in Unix<br />RMON: Remote Monitoring MIBs in SNMP<br />SLP: Service Location Protocol<br />SMTP: Simple Mail Transfer Protocol<br />SNMP: Simple Network Management Protocol<br />SNTP: Simple Network Time Protocol<br />Syslog Protocol<br />TELNET: TCP/IP Terminal Emulation Protocol<br />TFTP: Trivial File Transfer Protocol<br />URL: Uniform Resource Locator<br />XMPP: Extensible Messaging and Presence Protocol<br />X-Window: X Window or X Protocol or X System<br /><br /><br /> </pre> </div><p style="text-align: justify;" class="docText"><b>Presentation Layer</b> LPP: Lightweight Presentation Protocol </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Session Layer</b> RPC: Remote Procedure Call protocol </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Transport Layer</b> </p><div style="text-align: justify;"><pre>ITOT: ISO Transport Over TCP/IP<br />RDP: Reliable Data Protocol<br />RUDP: Reliable UDP<br />TALI: Transport Adapter Layer Interface<br />TCP: Transmission Control Protocol<br />UDP: User Datagram Protocol<br />Van Jacobson: Compressed TCP<br /></pre> </div><p style="text-align: justify;" class="docText"><b>Network Layer Routing</b> </p><div style="text-align: justify;"><pre>BGP/BGP-4: Border Gateway Protocol<br />EGP: Exterior Gateway Protocol<br />IP: Internet Protocol<br />IPv6: Internet Protocol version 6<br />ICMP/ICMPv6: Internet Control Message Protocol<br />IRDP: ICMP Router Discovery Protocol<br />Mobile IP: IP Mobility Support Protocol for IPv4 & IPv6<br />NARP: NBMA Address Resolution Protocol<br />NHRP: Next Hop Resolution Protocol<br />OSPF: Open Shortest Path First<br />RIP (RIP2): Routing Information Protocol<br />RIPng: RIP for IPv6<br />RSVP: Resource ReSerVation Protocol<br />VRRP: Virtual Router Redundancy Protocol<br /></pre> </div><p style="text-align: justify;" class="docText"><b>Multicast</b> </p><div style="text-align: justify;"><pre>BGMP: Border Gateway Multicast Protocol<br />DVMRP: Distance Vector Multicast Routing Protocol<br />IGMP: Internet Group Management Protocol<br />MARS: Multicast Address Resolution Server<br />MBGP: Multiprotocol BGP<br />MOSPF: Multicast OSPF<br />MSDP: Multicast Source Discovery Protocol<br />MZAP: Multicast-Scope Zone Announcement Protocol<br />PGM: Pragmatic General Multicast Protocol<br />PIM-DM: Protocol Independent Multicast - Dense Mode<br />PIM-SM: Protocol Independent Multicast - Sparse Mode<br /></pre> </div><p style="text-align: justify;" class="docText"><b>MPLS Protocols</b> </p><div style="text-align: justify;"><pre>MPLS: Multi-Protocol Label Switching<br />CR-LDP: Constraint-Based Label Distribution Protocol<br />LDP: Label Distribution Protocol<br />RSVP-TE: Resource ReSerVation Protocol-Traffic Engineering<br />GMPLS: Generalized Multi-Protocol Lable Switching<br /></pre> </div><p style="text-align: justify;" class="docText"><b>Data Link Layer</b> </p><div style="text-align: justify;"><pre>ARP and InARP: Address Resolution Protocol and Inverse ARP<br />IPCP and IPv6CP: IP Control Protocol and IPv6 Control Protocol<br />RARP: Reverse Address Resolution Protocol<br />SLIP: Serial Line IP<br /></pre> </div><p style="text-align: justify;" class="docText"><b>Related protocol suites</b> LAN, MAN, WAN, SAN, Security/VPN </p><div style="text-align: justify;"> </div><p style="text-align: justify;" class="docText"><b>Sponsor Source</b> IETF, DARPA, ISO</p><center> <p class="docText"><img id="" alt="" src="part06_files/getfile.png" border="0" /></p></center><br /></div></div></div></div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-8878497828215071973?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0tag:blogger.com,1999:blog-2364300410027338874.post-52121537428799629432009-07-14T06:45:00.000-07:002009-07-14T06:53:48.873-07:00TCP and UDP Port Numbers<p style="text-align: justify;" class="docText"><b>Description</b><a name="TCP and"></a> TCP and UDP are both transport protocols above the IP layer, which are interfaces between IP and upper-layer processes. TCP and UDP protocol port numbers are designed to distinguish multiple applications running on a single device with one IP address from one another. </p><p style="text-align: justify;" class="docText"><a name="applications may"></a>Since many network applications may be running on the same machine, computers need something to make sure the correct software application on the destination computer gets the data packets from the source machine, and to make sure replies get routed to the correct application on the source computer. This is accomplished through the use of the TCP or UDP "port numbers". In the TCP and UDP header, there are "Source Port" and "Destination Port" fields which are used to indicate the message sending process and receiving process identities defined. The combination of the IP address and the port number is called "socket".<br /></p><p style="text-align: justify;" class="docText"><a name="port ranges"></a>There are three port ranges defined by IETF IANA: the Well Known Ports, the Registered Ports, and the Dynamic and/or Private Ports.<br /></p><ul style="text-align: justify;"><li>The Well Known Ports are in the range of 0 to 1023, which are assigned by the IANA. In most cases, they can only be used by system (or root) processes or by programs executed by privileged users. </li><li style="text-align: justify;">The Registered Ports are in the range of 1024 to 49151, which are not controlled by IANA. They are commonly used by ordinary user processes or programs executed by ordinary users. </li><li style="text-align: justify;">The Dynamic and/or Private Ports are in the range of 49152 to 65535, which are typically used as source port by a TCP or UDP client, to communicate with a remote TCP or UDP server, using a well-known port as destination port. </li></ul><br /><p class="docText">Partial TCP UDP Port Numbers (Well-Known Ports) </p> <p class="docText"><a name="app01tb01"></a> </p><p style="text-align: justify;"> <table style="text-align: left; margin-left: 0px; margin-right: 0px; width: 628px; height: 2143px;" class="allBorders" border="1" cellspacing="0"> <colgroup align="left" span="5"> <col width="80"> <col width="80"> <col width="80"> <col width="80"> <col width="200"></colgroup> <thead></thead> <tbody> <tr> <td class="docTableCell" align="left">Port No.</td> <td class="docTableCell" align="left">Protocol</td> <td class="docTableCell" align="left">Service Name</td> <td class="docTableCell" align="left">Aliases</td> <td class="docTableCell" align="left">Comment</td></tr> <tr> <td class="docTableCell" align="left">1</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">tcpmux</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">TCP Port Service Multiplexer</td></tr> <tr> <td class="docTableCell" align="left">2</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">compressnet</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Management Utility</td></tr> <tr> <td class="docTableCell" align="left">3</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">compressnet</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Compression Process</td></tr> <tr> <td class="docTableCell" align="left">7</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">echo</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Echo</td></tr> <tr> <td class="docTableCell" align="left">13</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">daytime</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Daytime</td></tr> <tr> <td class="docTableCell" align="left">19</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">chargen</td> <td class="docTableCell" align="left">ttytst source</td> <td class="docTableCell" align="left">Character generator</td></tr> <tr> <td class="docTableCell" align="left">20</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">ftp-data</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">File Transfer</td></tr> <tr> <td class="docTableCell" align="left">21</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">ftp</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">FTP Control</td></tr> <tr> <td class="docTableCell" align="left">22</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">ssh</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">SSH remote login protocol</td></tr> <tr> <td class="docTableCell" align="left">23</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">telnet</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Telnet</td></tr> <tr> <td class="docTableCell" align="left">25</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">smtp</td> <td class="docTableCell" align="left">mail</td> <td class="docTableCell" align="left">Simple Mail Transfer</td></tr> <tr> <td class="docTableCell" align="left">37</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">Time</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Time</td></tr> <tr> <td class="docTableCell" align="left">39</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">RLP</td> <td class="docTableCell" align="left">resource</td> <td class="docTableCell" align="left">Resource Location Protocol</td></tr> <tr> <td class="docTableCell" align="left">42</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">nameserver</td> <td class="docTableCell" align="left">name</td> <td class="docTableCell" align="left">Host Name Server</td></tr> <tr> <td class="docTableCell" align="left">43</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">nicname</td> <td class="docTableCell" align="left">whois</td> <td class="docTableCell" align="left">Who Is</td></tr> <tr> <td class="docTableCell" align="left">49</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">TACACS</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">TACACS: Login Host Protocol</td></tr> <tr> <td class="docTableCell" align="left">53</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">domain</td> <td class="docTableCell" align="left">DNS</td> <td class="docTableCell" align="left">Domain Name Server</td></tr> <tr> <td class="docTableCell" align="left">67</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">bootps</td> <td class="docTableCell" align="left">dhcps</td> <td class="docTableCell" align="left">Bootstrap Protocol Server</td></tr> <tr> <td class="docTableCell" align="left">68</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">bootpc</td> <td class="docTableCell" align="left">dhcpc</td> <td class="docTableCell" align="left">Bootstrap Protocol Client</td></tr> <tr> <td class="docTableCell" align="left">69</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">TFTP</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Trivial File Transfer Protocol</td></tr> <tr> <td class="docTableCell" align="left">70</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">gopher</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Gopher</td></tr> <tr> <td class="docTableCell" align="left">79</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">finger</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Finger</td></tr> <tr> <td class="docTableCell" align="left">80</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">http</td> <td class="docTableCell" align="left">www,http</td> <td class="docTableCell" align="left">World Wide Web</td></tr> <tr> <td class="docTableCell" align="left">88</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">kerberos</td> <td class="docTableCell" align="left">krb5</td> <td class="docTableCell" align="left">Kerberos</td></tr> <tr> <td class="docTableCell" align="left">101</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">hostname</td> <td class="docTableCell" align="left">hostnames</td> <td class="docTableCell" align="left">NIC Host Name Server</td></tr> <tr> <td class="docTableCell" align="left">102</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">iso-tsap</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">ISO-TSAP Class 0</td></tr> <tr> <td class="docTableCell" align="left">107</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">rtelnet</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Remote Telnet Service</td></tr> <tr> <td class="docTableCell" align="left">110</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Pop3</td> <td class="docTableCell" align="left">postoffice</td> <td class="docTableCell" align="left">Post Office Protocol- Version 3</td></tr> <tr> <td class="docTableCell" align="left">111</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">sunrpc</td> <td class="docTableCell" align="left">rpcbind portmap</td> <td class="docTableCell" align="left">SUN Remote Procedure Call</td></tr> <tr> <td class="docTableCell" align="left">113</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Auth</td> <td class="docTableCell" align="left">ident tap</td> <td class="docTableCell" align="left">Authentication Sevice</td></tr> <tr> <td class="docTableCell" align="left">117</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Uucppath</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">UUCP Path Service</td></tr> <tr> <td class="docTableCell" align="left">118</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">sqlserv</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">SQL Services</td></tr> <tr> <td class="docTableCell" align="left">119</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">nntp</td> <td class="docTableCell" align="left">usenet</td> <td class="docTableCell" align="left">Network News Transfer Protocol</td></tr> <tr> <td class="docTableCell" align="left">123</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Ntp</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Network Time Protocol</td></tr> <tr> <td class="docTableCell" align="left">135</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">epmap</td> <td class="docTableCell" align="left">loc-srv</td> <td class="docTableCell" align="left">DCE endpoint resolution</td></tr> <tr> <td class="docTableCell" align="left">137</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">netbiosns</td> <td class="docTableCell" align="left">nbname</td> <td class="docTableCell" align="left">NETBIOS Name Service</td></tr> <tr> <td class="docTableCell" align="left">138</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">netbiosdgm</td> <td class="docTableCell" align="left">nbdatagram</td> <td class="docTableCell" align="left">NETBIOS Datagram Service</td></tr> <tr> <td class="docTableCell" align="left">139</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">netbiosssn</td> <td class="docTableCell" align="left">nbsession</td> <td class="docTableCell" align="left">NETBIOS Session Service</td></tr> <tr> <td class="docTableCell" align="left">143</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Imap</td> <td class="docTableCell" align="left">imap4</td> <td class="docTableCell" align="left">Internet Message Access Protocol</td></tr> <tr> <td class="docTableCell" align="left">158</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">pcmailsrv</td> <td class="docTableCell" align="left">repository</td> <td class="docTableCell" align="left">PC Mail Server</td></tr> <tr> <td class="docTableCell" align="left">161</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">snmp</td> <td class="docTableCell" align="left">snmp</td> <td class="docTableCell" align="left">SNMP</td></tr> <tr> <td class="docTableCell" align="left">162</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">snmptrap</td> <td class="docTableCell" align="left">snmptrap</td> <td class="docTableCell" align="left">SNMP TRAP</td></tr> <tr> <td class="docTableCell" align="left">170</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Printsrv</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Network PostScript</td></tr> <tr> <td class="docTableCell" align="left">194</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">irc</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Internet Relay Chat Protocol</td></tr> <tr> <td class="docTableCell" align="left">213</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">ipx</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">IPX over IP</td></tr> <tr> <td class="docTableCell" align="left">389</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">ldap</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Lightweight Directory Access Protocol</td></tr> <tr> <td class="docTableCell" align="left">401</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">UPS</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Uninterruptible Power Supply</td></tr> <tr> <td class="docTableCell" align="left">443</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">https</td> <td class="docTableCell" align="left">MCom</td> <td class="docTableCell" align="left">http protocol over TLS/SSL</td></tr> <tr> <td class="docTableCell" align="left">445</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">CIFS</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Kerberos (v5)</td></tr> <tr> <td class="docTableCell" align="left">464</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">kpasswd</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Message</td></tr> <tr> <td class="docTableCell" align="left">500</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">isakmp</td> <td class="docTableCell" align="left">ike</td> <td class="docTableCell" align="left">Internet Key Exchange (IPSec)</td></tr> <tr> <td class="docTableCell" align="left">513</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">login</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Remote Login</td></tr> <tr> <td class="docTableCell" align="left">513</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">who</td> <td class="docTableCell" align="left">whod</td> <td class="docTableCell" align="left">Database of who's logged on, average load</td></tr> <tr> <td class="docTableCell" align="left">514</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">cmd</td> <td class="docTableCell" align="left">shell</td> <td class="docTableCell" align="left">Automatic Authentication</td></tr> <tr> <td class="docTableCell" align="left">514</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">syslog</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left"><br /></td></tr> <tr> <td class="docTableCell" align="left">515</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">printer</td> <td class="docTableCell" align="left">spooler</td> <td class="docTableCell" align="left">Listens for incoming connections</td></tr> <tr> <td class="docTableCell" align="left">517</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">talk</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Establishes TCP Connection</td></tr> <tr> <td class="docTableCell" align="left">120</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">efs</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Extended File Name Server</td></tr> <tr> <td class="docTableCell" align="left">520</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Routing</td> <td class="docTableCell" align="left">router routed</td> <td class="docTableCell" align="left">RIPv.1, RIPv.2</td></tr> <tr> <td class="docTableCell" align="left">521</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Routing</td> <td class="docTableCell" align="left">router routed</td> <td class="docTableCell" align="left">RIPng</td></tr> <tr> <td class="docTableCell" align="left">525</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Timed</td> <td class="docTableCell" align="left">timeserver</td> <td class="docTableCell" align="left">Timeserver</td></tr> <tr> <td class="docTableCell" align="left">530</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">Courier</td> <td class="docTableCell" align="left">rpc</td> <td class="docTableCell" align="left">RPC</td></tr> <tr> <td class="docTableCell" align="left">531</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">conference</td> <td class="docTableCell" align="left">chat</td> <td class="docTableCell" align="left">IRC Chat</td></tr> <tr> <td class="docTableCell" align="left">532</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">netnews</td> <td class="docTableCell" align="left">readnews</td> <td class="docTableCell" align="left">Readnews</td></tr> <tr> <td class="docTableCell" align="left">533</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Netwall</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">For emergency broadcasts</td></tr> <tr> <td class="docTableCell" align="left">540</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Uucp</td> <td class="docTableCell" align="left">uucpd</td> <td class="docTableCell" align="left">Uucpd</td></tr> <tr> <td class="docTableCell" align="left">543</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Klogin</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Kerberos login</td></tr> <tr> <td class="docTableCell" align="left">544</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Kshell</td> <td class="docTableCell" align="left">krcmd</td> <td class="docTableCell" align="left">Kerberos remote shell</td></tr> <tr> <td class="docTableCell" align="left">550</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">newrwho</td> <td class="docTableCell" align="left">new-who</td> <td class="docTableCell" align="left">New-who</td></tr> <tr> <td class="docTableCell" align="left">554</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">rtsp</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Real Time Stream Control Protocol</td></tr> <tr> <td class="docTableCell" align="left">556</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">remotefs</td> <td class="docTableCell" align="left">rfs rfs_server</td> <td class="docTableCell" align="left">Rfs Server</td></tr> <tr> <td class="docTableCell" align="left">560</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">rmonitor</td> <td class="docTableCell" align="left">rmonitord</td> <td class="docTableCell" align="left">Rmonitor</td></tr> <tr> <td class="docTableCell" align="left">561</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">monitor</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left"><br /></td></tr> <tr> <td class="docTableCell" align="left">636</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">Ldaps</td> <td class="docTableCell" align="left">sldap</td> <td class="docTableCell" align="left">LDAP over TLS/SSL</td></tr> <tr> <td class="docTableCell" align="left">749</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">kerberosadm</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Kerberos administration</td></tr> <tr> <td class="docTableCell" align="left">750</td> <td class="docTableCell" align="left">UDP</td> <td class="docTableCell" align="left">Kerberos-iv</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">Kerberos version IV</td></tr> <tr> <td class="docTableCell" align="left">1080</td> <td class="docTableCell" align="left">TCP/UDP</td> <td class="docTableCell" align="left">socks</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">socks</td></tr> <tr> <td class="docTableCell" align="left">1812</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">RADIUS</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">RADIUS</td></tr> <tr> <td class="docTableCell" align="left">1813</td> <td class="docTableCell" align="left">TCP</td> <td class="docTableCell" align="left">RADIUS</td> <td class="docTableCell" align="left"><br /></td> <td class="docTableCell" align="left">RADIUS accounting</td></tr></tbody></table></p><br /> <p class="docText"><b>Reference Links</b> </p><pre><a class="docLink" href="http://www.iana.org/assignments/port-numbers" target="_blank">http://www.iana.org/assignments/port-numbers</a><br />TCP and UDP port numbers<br /></pre><span style="font-weight: bold;"><br /></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2364300410027338874-5212153742879962943?l=faknewbehandbook.blogspot.com'/></div>fakrule bromonoreply@blogger.com0