Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />INTRODUCTION<br /><br />The goal of this manual is to teach the basic concepts of computer networks, but the idea is for it to be fun and an enjoyable read; there will be plenty of analogies and jokes to achieve maximum understanding, without leaving aside the technicalities required to properly grasp the subject.<br /><br />On the other hand, this text was born as an initiative from our beloved Underc0de community for the newest users who are just starting their journey in this wonderful world of technology, to try to give them the nuances needed to understand the tons of information that fill our forum.<br /><br />So, without further ado, it's time to begin.<br /><br />1.- IN THE BEGINNING...<br /><br />Communication has always been a human need, and we could apply the definition we were given since we were kids, so broadly speaking communication is:<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />"The action in which two or more subjects (sender and receiver), through some kind of channel, exchange information and ideas using a common code (language)."<br /><br />We could complicate our lives and fill half a page with many more concepts, but that is not the idea of "Underc0de", so from here on this is the definition we will use to guide us, and it is the one that will be cited as the manual progresses.<br /><br />In bygone times, communication only required knowing the language (code) of another person acting as the other party, because as you can imagine, talking alone doesn't make much sense (laughs). But since humanity never stops evolving, we began to notice that we could only communicate with people close to us and only at the moment we were with those people; we thus noticed that we were limited by "time" and "space"; and we simply couldn't leave it like that.<br /><br />1.1- Beyond time<br /><br />When we realized that our ideas did not last beyond death, we intensely searched for some method that would let us defeat time; and that is when writing was born (more than 10,000 years ago), allowing us to leave a mark that transcends time. <br /><br />1.2- Beyond space<br /><br />This is the really interesting part, that is, when we discovered how to communicate across considerable distances. At first there were smoke signals that managed to transmit complete messages from one watchtower to another, and around 1940 the first transmission of information by electrical/electronic means took place, circumstances that marked the beginning of communication using technology; at that precise moment, what today is "a computer network" was first glimpsed.<br /><br /><br />2.- COMPUTER NETWORKS<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />After the tough beginnings -and approximately in the mid '60s- the first computers started to appear that used the telephone network to share files using a modem. It is said that at the beginning speeds were little more than 1200 bps, and the last Dial-up connections reached the dizzying and astonishing speed of 56 kbps! If you're over 28, you very likely had one of those modems at home. Do you remember that magical sound of two machines negotiating a connection...? (tears come to my eyes); well, with the arrival of computer networks, a door opened to magnificent horizons never imagined before.<br /><br /><br />2.1- HOW DOES "THIS" COMPUTER NETWORK THING WORK<br /><br />Just like in ancient times, today we need to communicate across continents and seas in a secure and reliable way, and for that we need several elements:<br /><br />a.- A platform/infrastructure.<br /><br />We need a whole set of devices that work in a common order: network cards, routers, modems, switches, cables, etc... They all work within some previously established standard.<br /><br />b.- A set of rules that structure communication is needed.<br /><br />If an English speaker tries to start a conversation with someone who speaks the same language, they most likely won't have any trouble understanding each other and the result will be successful communication, but imagine a Spanish speaker trying to start a conversation with a Russian (I don't think they could communicate even with smoke signals).<br /><br />In computer networks, ideally everyone speaks the same language, which ensures proper communication.<br /><br /><br />2.2- TYPES OF NETWORKS<br /><br />Networks can be classified by several factors, but in this installment we will only cover two:<br /><br />a.- Size.<br /><br />According to their size, networks can be:<br /><br />I.- Small (< 200 computers)<br />II.- Medium (200 - 1000 computers)<br />III.- Large (> 1000 computers)<br /><br />b.- Topology.<br /><br />I.- LAN (Local Area Network, those wired ones we have at home).<br />II.- WLAN (Wireless Local Area Network, they're the trend since all home modems come enabled to provide wireless connections).<br /><br />There are more topologies, somewhat complex, but remember this is just the appetizer and the idea is not to complicate things, since we want to give you the nuances of how networks work, so stay with me.<br /><br /><br />2.3.- WHAT "LANGUAGE" IS SPOKEN IN COMPUTER NETWORKS?<br /><br /><br />Well, just like in every kind of communication, here we need a common "language" so our computers can communicate with each other, and in the world of networks that language has a name: it's called "TCP/IP". Legend has it that it was designed by Vinton Cerf and Robert Khan in 1972, which means that while our parents were busy falling in love and all that, these gentlemen were developing something that would change the world completely... and they succeeded.<br /><br />2.3.1.- HOW DOES TCP/IP WORK?<br /><br />Defining Mr. TCP/IP as a single thing would be a mistake, I think, so I consider it more appropriate to say that: "It is a set of rules and operating standards that make effective communication between machines on a network possible"; I could give a more technical and perhaps more complex definition, but I'll say it again: that is not the idea of this material, so I propose a mental exercise: we'll tell a story and I'll explain the rest afterwards.<br /><br />"The letter"<br /><br />"This morning I decided to send a letter to my mother who lives in Canada, so I took some paper and wrote my letter. When I finished it I put it in an envelope and dropped it in my city's post office mailbox. But it turns out the employees who sort shipments at the post office returned my letter because I hadn't specified the destination address. I was surprised at my own level of stupidity and also sad because in the end my letter couldn't arrive."<br /><br />Very well, that was my little story about how a letter didn't reach its destination; now the obvious question arises: <br /><br />"Why didn't my letter arrive?"<br /><br />Answer: It didn't arrive because I didn't put the destination address on it.<br /><br />Well, in the world of networks we need to specify who we want to deliver the letters to (from now on, packets), and Mr. TCP/IP's favorite way is for packets to have a specified destination address; otherwise they won't successfully reach their destination, and that's how something very often mentioned around here appears: "IP addresses"<br /><br />2.3.1.1 WHAT IS AN IP ADDRESS?<br /><br />"Well, an IP address is a set of numbers by which a network or a computer within that same network can be specified"; it's the way the chubby Mr. TCP/IP identifies destinations. While in human life addresses consist of city, district, street and house number, machines can't understand those things, so here addresses look like this:<br /><br />192.168.1.1<br />172.16.1.1<br />10.0.0.1<br /><br /><br />2.3.2.- WHAT IS THE PATH OF PACKETS LIKE?<br /><br />Well, Mr. TCP/IP now knows the destination of the packets; now the question arises of how to get them to their destination, and here's another fun story:<br /><br />"Mr. Rutenio works sorting letters at the local post office. Every day he goes diligently to his job, which consists of sorting shipments according to their [destination address], and he simply does it by reading the envelopes of the letters; he never knows the content, he just reads the envelopes to sort the mail correctly. That way, letters going to Germany are put in the Germany box, those going to Canada in the Canada box, and so on, until the end of the day when he goes home to rest."<br /><br />As you'll have noticed, thanks to "the address" Mr. Rutenio can determine where to send each letter; and that is exactly what happens in the world of networks.<br /><br />The Router (a close relative of Mr. Rutenio) looks in each packet for a destination IP address indicating where to send that packet, but perhaps more than one of you is wondering: "ok Cloudswx, but what's this packet thing?".<br /><br />2.3.2.1.- WHAT IS A PACKET<br /><br />I don't know, I'm thinking about whether I should describe it or whether it's better to tell a story; the truth is I love stories and I also love technology, so for me there's nothing better than explaining technology with a good story, let's get to it.<br /><br />"On a sunny day in my city I decided to board the bus that goes downtown, when suddenly the ground began to shake and the sky went dark. All of us on board got pretty scared and decided to run off the bus, but what a surprise when we realized we couldn't all get out at the same time (because of the narrow door). In the midst of desperation, a chubby gentleman named TCP/IP told us it would be better if we took turns and got out one by one. The suggestion was great, since we were able to solve our terrible problem given that the earthquake was about to destroy our bus."<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />Phew, I was lucky and saved thanks to TCP/IP. Well, in networks packets can't all go through at the same time, as it's far from ideal and not very precise; that's why information is cut into smaller pieces called packets, which take turns going out to travel the network. <br /><br />If right now you're listening to music online and browsing at the same time, it might seem like you're doing everything simultaneously, but I'm sorry to disappoint you by saying it's an illusion of the machine world (this is the Matrix). Your network actually alternates your connection between the music and your browsing, but it does it so fast you don't notice, and this phenomenon is known as "multiplexing."<br /><br /><br />2.3.3.- WHAT IS THE PATH OF PACKETS MADE OF?<br /><br /><br />Well, we're understanding Mr. TCP/IP more and more; we already know what an IP address is, what a packet is and how it is forwarded or routed to its destination, but wait a moment... <br /><br />We still don't know what our packets' path is made of...<br /><br />Nor do we know how many times our packet must transform its nature to travel along those paths, so let's explain (this time without stories, let's get serious).<br /><br />As I explained earlier, communications in the digital world have a very peculiar and limited alphabet, based on "ones" and "zeros"; but don't be fooled, that simplicity also makes it very easy and convenient to transmit and interpret, so let's do a few mental exercises to absorb the concept:<br /><br />1 = noise voltage light <br />0 = silence absence of voltage darkness<br /><br /><br />Now knowing this, let's imagine we must find a way to transmit "ones" and "zeros" over a copper cable. We can simply assign a voltage value as "1" and its absence would be "0", and at the other end our receiver knows how it must interpret the changes, and that's it! Broadly speaking, that's how packets are transmitted over a copper cable.<br /><br />Now let's imagine we must do it using light... Hmmm.... Interesting, well the behavior is the same: we assign "1" to a pulse of light and "0" to darkness and that's it! That's how packets are transmitted over optical fiber.<br /><br />And if we had to do it using old modems (tears in my eyes again) we would use a sequence of noises and silences to represent "1" and "0"<br /><br />So we could say that our packets' path can be made of anything, as long as we manage to assign states for our "ones" and our "zeros". Every time humanity finds a new way to transmit, a standard is created<br /><br /><br />3.- COMPUTER NETWORK PROTOCOLS<br /><br />As I wrote earlier, proper communication requires a series of mechanisms and rules that define and give meaning to the way machines greet and talk to each other, but... wait a moment... <br /><br />What do you mean machines greet each other?<br /><br />Well yes, machines greet each other before establishing a connection, and that's because Mr. TCP/IP is very polite and before starting to send packets he must be sure someone on the other side is waiting for them; he must also establish the speed at which they'll talk and several other things, and all of this is achieved with a series of greetings consisting of 3 steps:<br /><br />The sender greets with:<br /><br />-"Hi there, how are you? Could I send you some packets?" (SYN)<br /><br />And the receiver replies:<br /><br />-"Ok, I got your greeting and I totally agree" (SYN-ACK)<br /><br />To which the sender finishes by saying:<br /><br />-"Ok then, here come my packets" (ACK)<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />That's how a connection is established between two devices on a network.<br /><br /><br />3.1 THE CHILDREN OF MR. TCP/IP<br /><br />Mr. TCP/IP has two children: one is somewhat rebellious and careless but very fast, while the other is very dedicated and attentive to detail. We'll meet them after explaining the following.<br /><br />Networks must be reliable, and I don't mean their security; I mean they must provide mechanisms to ensure the transmission of the "ones" and "zeros", so there must be an acknowledgment of receipt for each packet sent (or for each group of them), and that is the rule established by the fat gentleman, but let's see what his children are like and how each of them works.<br /><br />Los enlaces son solo para miembros. Registrate o iniciá sesión
<br /><br />a.- TCP<br /><br />He has almost the same name as his father, his initials stand for "Transmission Control Protocol", and he is very strict about his father's rules: he sends packets normally, but demands an acknowledgment for each packet, and if he doesn't receive it he doesn't send the next packet but resends the same one until he confirms the packet was delivered. He is very reliable and precise but slow, since he must process each packet and wait for an acknowledgment before sending the next one.<br /><br />b.- UDP<br /><br />He is TCP's younger brother and doesn't worry much about ensuring each packet; he doesn't care, his only goal is to send all packets as fast as possible without worrying whether they were received or not. He is neither reliable nor precise, but he is much faster than his brother.<br /><br /><br />We might then ask: "And why would I need to use that rebel UDP?" The answer depends a lot on our needs since, for example, a download from the Internet needs to be completed with all its packets; none can be lost, otherwise the download would be in vain, and in this case TCP is used. But if instead we need to watch video online, listen to music online and such things... what matters most is speed and it doesn't matter if a packet is lost (a millisecond of music, one pixel less on screen, etc...); in this latter case UDP is used.<br /><br /> <br />I think it's simple and clear, right?<br /><br /><br />To be continued...<br /> <br />Until next time!
<br /><br /><br /><br />