![]() ![]() For example when using a different physical connections (e.g. ![]() By describing the networking protocols in layers it allows the layer to be changed without affecting other layers. The OSI model splits the different functions of networking into different layers. This is a model to describe the different networking functionality by the Open Standards Institute. Networking protocols are often described relating to the OSI model. It's also possible for the sesssion to be handled higher up the networking stack (but I'm getting ahead of myself here). Whereas for some less important data you may just want to send and forget it with the hope it will reach the other end. For each data packet being sent a confirmation has to be generated and even if there is no data being sent there will often be some kind of keep alive signal. The reason for this is that there is a lot of overhead involved in TCP. Or if the person has moved house they may never receive the letter.Īt first it may sound that there is no reason to choose UDP over TCP after all if you can have the extra reassurance then why would you care about UDP. After you have posted the letter it could be lost or destroyed on it’s way to it’s destination. ![]() With the postal system after you post the letter then you do not know for certain whether or not the mail will be received. If you were disconnected during the telephone conversation then you would know about it and be able to phone the other person again. With the telephone when you establish a connection with the other person, you know for certain that the user receives the message. An application can run on top of UDP and implement it's own checking that each packet is received, but that is not the same as leaving it to the networking stack to implement.Ī common way of comparing these is to liken TCP to the telephone system and UDP to the postal service. For UDP each data packet is sent but there is no checking that it has been received, or anyway of resending within the network layers. In other words when TCP is being used there is a session setup between the hosts and the transfer is guaranteed. The difference between TCP and UDP is that TCP is connection based protocol whereas UDP is connectionless. These can be integral to the operation of the networking, such as the Domain Name System or could be an application that uses the network such as E-mail (both of these are discussed in further detail later).Īnother related protocol is UDP (User Datagram Protocol) which also runs on top of the IP (Internet Protocol). These provide different functionality important to the exchange of data over the networks. Within the TCP/IP networking protocol there are lots more protocols. It is an open standard so can be implemented on any computer with the appropriate physical attributes. The protocol is effectively a set of rules that describe how the data is passed between the computers. It is a set of protocols that define how two or more computers can communicate with each other. TCP/IP is an abbreviation for Transmission Control Protocol / Internet Protocol. A shortage of remaining IPV4 addresses is encouraging a more agressive push towards IPV6 over the next few years. This is primarily aimed at the current IP Version 4, although an introduction to IP Version 6 is included. With the success of the Internet this is the dominant protocol in use almost exclusively today. A future tutorial will provide the specific commands and files which provide the configuration on Linux systems.Īlthough there are other types of network this guide will only cover TCP/IP networking. Although intended for an audience of Linux users and administrators, the contents of this will apply equally to other operating systems or networking devices. This reference guide will discuss the basics of TCP/IP networking. TCP/IP networking reference guide Introduction ![]()
0 Comments
Leave a Reply. |