WEBVTT - What is a router?

0:00:00.280 --> 0:00:02.960
<v Speaker 1>Brought to you by the reinvented two thousand twelve Camray.

0:00:03.160 --> 0:00:08.840
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.000 --> 0:00:17.560
<v Speaker 1>tech Stuff from how stuff works dot com. Hello everyone,

0:00:17.640 --> 0:00:20.560
<v Speaker 1>welcome to tech stuff. My name is Chris Polette. I'm

0:00:20.600 --> 0:00:23.400
<v Speaker 1>an editor at how stuff works dot com, and as usual,

0:00:23.960 --> 0:00:26.960
<v Speaker 1>sitting across from me, I have senior writer Jonathan Strickland.

0:00:27.200 --> 0:00:31.920
<v Speaker 1>We're on a road to nowhere, which just goes to

0:00:31.960 --> 0:00:33.880
<v Speaker 1>show you that we're not a couple of talking heads.

0:00:33.960 --> 0:00:37.199
<v Speaker 1>That's right, Before we get into this topic, we have

0:00:37.640 --> 0:00:40.160
<v Speaker 1>actually it's a two fur First, we have a little

0:00:40.720 --> 0:00:49.080
<v Speaker 1>listener mail. This listener mail comes from Sam, and Sam says, Hello,

0:00:49.159 --> 0:00:51.080
<v Speaker 1>John and Chris. I really enjoy your show and I

0:00:51.120 --> 0:00:53.880
<v Speaker 1>appreciate all the wonderful information you provide about various tech

0:00:53.960 --> 0:00:56.000
<v Speaker 1>Keep up the good work, could you, guys, perhaps to

0:00:56.040 --> 0:00:58.400
<v Speaker 1>a podcast that covers how network routers such as links

0:00:58.440 --> 0:01:01.160
<v Speaker 1>Us and other's work for and their role in office

0:01:01.160 --> 0:01:03.240
<v Speaker 1>and home networks. That'd be swell if you did. Thank

0:01:03.240 --> 0:01:06.559
<v Speaker 1>you guys for making such entertaining yet informative podcast. Cheers. PS.

0:01:06.760 --> 0:01:09.679
<v Speaker 1>Is there any chance that the old listener mail audio

0:01:09.720 --> 0:01:12.360
<v Speaker 1>clip might be played again? You know, the one with

0:01:12.440 --> 0:01:14.360
<v Speaker 1>the annoying alarm. I like the new one, and I

0:01:14.360 --> 0:01:15.840
<v Speaker 1>know it is stuck, but there are times where I

0:01:15.920 --> 0:01:19.840
<v Speaker 1>yearned to hear the old one. Sam. This is for you.

0:01:20.040 --> 0:01:24.080
<v Speaker 1>Everyone else, please turn down the volume on your your

0:01:24.160 --> 0:01:27.640
<v Speaker 1>various playback devices. You have been warned, and now that

0:01:27.720 --> 0:01:31.120
<v Speaker 1>I have warned you, here comes a little old school

0:01:31.160 --> 0:01:41.160
<v Speaker 1>sound effect for listener. But on top of the listener

0:01:41.160 --> 0:01:43.760
<v Speaker 1>mail that we just read from Sam from Austin, Texas,

0:01:43.800 --> 0:01:48.000
<v Speaker 1>we also had a little Facebook feedback you be This

0:01:48.080 --> 0:01:49.840
<v Speaker 1>comes from Scott, who says, Hey, I was wondering if

0:01:49.840 --> 0:01:52.240
<v Speaker 1>you guys could do a podcast about routers, the different

0:01:52.320 --> 0:01:55.640
<v Speaker 1>uses for them and which is best for gaming, streaming, video, etcetera.

0:01:55.840 --> 0:01:58.200
<v Speaker 1>Thanks so much. Your episode on I p V six

0:01:58.280 --> 0:02:00.960
<v Speaker 1>was great and the number of IP address as was nuts.

0:02:01.080 --> 0:02:03.120
<v Speaker 1>You're telling me, Scott, I'm still trying to get my

0:02:03.160 --> 0:02:06.400
<v Speaker 1>breath back. So we are going to talk about routers.

0:02:06.400 --> 0:02:09.000
<v Speaker 1>And before we get too far into this, I want

0:02:09.040 --> 0:02:11.840
<v Speaker 1>to say we have some great articles on how stuff

0:02:11.880 --> 0:02:14.240
<v Speaker 1>works dot Com about routers, so if you want to

0:02:14.280 --> 0:02:17.640
<v Speaker 1>get more information, I recommend checking out how routers work,

0:02:17.680 --> 0:02:20.600
<v Speaker 1>also how network address translation works. Both of those are

0:02:20.600 --> 0:02:23.920
<v Speaker 1>going to be important in this discussion. Um, so let's

0:02:23.960 --> 0:02:26.639
<v Speaker 1>talk about what a roller is and what it does

0:02:26.720 --> 0:02:31.920
<v Speaker 1>and why it's important, yes, and talking about what value

0:02:31.960 --> 0:02:34.680
<v Speaker 1>it has to the Internet. Let's just say there wouldn't

0:02:34.720 --> 0:02:40.840
<v Speaker 1>be one without routers because you know, of course, the

0:02:40.880 --> 0:02:45.079
<v Speaker 1>Internet is a network of computers. It's just networks. Yes,

0:02:45.120 --> 0:02:47.960
<v Speaker 1>it's exactly. It's a it's a basically, it's a vast

0:02:48.639 --> 0:02:52.639
<v Speaker 1>system of computers talking to one another via multiple networks

0:02:52.840 --> 0:02:55.840
<v Speaker 1>and protocols. So yes, well yeah, they use the protocols

0:02:55.840 --> 0:02:57.880
<v Speaker 1>to talk to us. But yeah, I mean you have

0:02:58.560 --> 0:03:01.160
<v Speaker 1>you might have only one computer in your house and

0:03:01.240 --> 0:03:04.480
<v Speaker 1>it hooks up to you know, the networks at the

0:03:04.520 --> 0:03:08.120
<v Speaker 1>Internet service provider, and then those go to other networks

0:03:08.160 --> 0:03:10.160
<v Speaker 1>and it just goes on and on and on. Or

0:03:10.200 --> 0:03:13.519
<v Speaker 1>you might even have multiple computers in your house running

0:03:13.520 --> 0:03:16.880
<v Speaker 1>on another network which is attached to the other networks.

0:03:17.320 --> 0:03:19.840
<v Speaker 1>That's why they call it a cloud, because there's no

0:03:20.240 --> 0:03:22.880
<v Speaker 1>definite shape to the Internet. It all. It all depends

0:03:22.919 --> 0:03:25.360
<v Speaker 1>on what's on and what's off at any given time,

0:03:25.919 --> 0:03:28.480
<v Speaker 1>and these routers make it possible, especially when you do

0:03:28.600 --> 0:03:31.200
<v Speaker 1>have one line coming into your house and you have

0:03:31.360 --> 0:03:35.400
<v Speaker 1>multiple computers. Yeah, So what routers allow is the transfer

0:03:35.440 --> 0:03:40.080
<v Speaker 1>of information across different layers of communication. Now, what I

0:03:40.120 --> 0:03:43.680
<v Speaker 1>mean by that is that the Open Systems inter Connection

0:03:43.800 --> 0:03:48.360
<v Speaker 1>or os I model of communication divides up communication into

0:03:48.600 --> 0:03:52.040
<v Speaker 1>seven layers. And uh, really we're just going to be

0:03:52.080 --> 0:03:54.680
<v Speaker 1>thinking about the first three layers here. Actually now I'm

0:03:54.680 --> 0:03:57.520
<v Speaker 1>thinking about seven layer bars. Yeah, I'm thinking about seven

0:03:57.560 --> 0:04:02.920
<v Speaker 1>layer dip so um dip so. The the the seven

0:04:03.000 --> 0:04:05.800
<v Speaker 1>layers are. This was a system that was proposed by

0:04:05.920 --> 0:04:09.960
<v Speaker 1>Charles Bachman of a Honeywell Information Services. Honeywell, of course,

0:04:10.000 --> 0:04:12.440
<v Speaker 1>is one of those big names that's important in uh

0:04:12.480 --> 0:04:15.560
<v Speaker 1>in computer science. Yeah, they they've done all kinds of

0:04:15.560 --> 0:04:20.480
<v Speaker 1>technological things. Yes, So the seven layers are sort of

0:04:20.560 --> 0:04:23.719
<v Speaker 1>as a concepts so that you can break down what

0:04:23.880 --> 0:04:28.520
<v Speaker 1>sort of communication happens between various components within a communication system.

0:04:28.560 --> 0:04:30.520
<v Speaker 1>And it's uh so that you can really figure out,

0:04:30.520 --> 0:04:33.200
<v Speaker 1>all right, well, how do we have these various layers

0:04:33.240 --> 0:04:36.359
<v Speaker 1>interact with one another, which ones need to be, you know,

0:04:36.440 --> 0:04:39.360
<v Speaker 1>segregated from the rest and uh and just kind of

0:04:39.400 --> 0:04:42.760
<v Speaker 1>a way of defining it, at least from an ideal

0:04:43.160 --> 0:04:47.080
<v Speaker 1>perspective as opposed to necessarily a physical one. But layer

0:04:47.160 --> 0:04:49.520
<v Speaker 1>one is what we call the bit layer it's the

0:04:49.520 --> 0:04:53.120
<v Speaker 1>physical layer of data communication. So we're talking about physical

0:04:53.160 --> 0:04:56.680
<v Speaker 1>elements such as pens and uh the voltage, it's act

0:04:56.800 --> 0:05:00.040
<v Speaker 1>also electrical layout. It's the voltage that you need it

0:05:00.160 --> 0:05:04.560
<v Speaker 1>transfer information. And really you're talking about a single device

0:05:05.320 --> 0:05:09.520
<v Speaker 1>communicating through some sort of medium. So this is where

0:05:09.520 --> 0:05:12.760
<v Speaker 1>we were talking about one device. We're not connecting it

0:05:12.800 --> 0:05:16.640
<v Speaker 1>to anything else at on a layer one layer of communication.

0:05:17.080 --> 0:05:21.680
<v Speaker 1>Layer two is where we start talking about communication between devices,

0:05:22.040 --> 0:05:24.920
<v Speaker 1>and in this case we're talking about communication between devices

0:05:24.960 --> 0:05:29.000
<v Speaker 1>within a local area network or land. All right, so

0:05:29.720 --> 0:05:32.960
<v Speaker 1>a land you do not need a router. We actually

0:05:32.960 --> 0:05:37.440
<v Speaker 1>had another fellow right in UM recently on on our

0:05:37.440 --> 0:05:41.880
<v Speaker 1>Facebook page, I posted a quiz about routers, and he

0:05:42.000 --> 0:05:45.320
<v Speaker 1>pointed out that actually this is Carl who said this

0:05:45.440 --> 0:05:47.839
<v Speaker 1>is called me pedantic. But question one, A home network

0:05:47.880 --> 0:05:50.960
<v Speaker 1>does not require a router to operate either. Carl is

0:05:51.000 --> 0:05:53.960
<v Speaker 1>absolutely correct. You do not need a router to allow

0:05:54.000 --> 0:05:57.160
<v Speaker 1>communication within a local area network. You need a switch

0:05:57.600 --> 0:05:59.720
<v Speaker 1>that can switch the data back and forth, but you

0:05:59.760 --> 0:06:02.920
<v Speaker 1>don't need a router. Right, So this is layer to

0:06:03.120 --> 0:06:05.520
<v Speaker 1>all that all that communication within layer two within a

0:06:05.560 --> 0:06:10.520
<v Speaker 1>local area network, a single network can be uh controlled

0:06:10.520 --> 0:06:12.760
<v Speaker 1>through a switch. You don't have to worry about a

0:06:12.839 --> 0:06:15.920
<v Speaker 1>router at that point. Now, if you want to communicate

0:06:15.960 --> 0:06:19.360
<v Speaker 1>to a device, it's on another network. This is where

0:06:19.360 --> 0:06:22.640
<v Speaker 1>the Internet comes in. The Internet is that network of networks.

0:06:22.680 --> 0:06:25.520
<v Speaker 1>So let's say I want to visit a website and

0:06:25.560 --> 0:06:29.400
<v Speaker 1>the server that has that websites information on it is

0:06:29.480 --> 0:06:31.919
<v Speaker 1>not on my local area network, but is on some

0:06:32.160 --> 0:06:35.279
<v Speaker 1>other network, possibly on the other side of the world.

0:06:35.920 --> 0:06:38.240
<v Speaker 1>That's when you need a router, because what the router

0:06:38.400 --> 0:06:42.160
<v Speaker 1>does is it controls the the information moving from your

0:06:42.200 --> 0:06:46.200
<v Speaker 1>local area network to the Internet so that it will

0:06:46.240 --> 0:06:49.320
<v Speaker 1>go to the proper place. And it also receives information

0:06:49.360 --> 0:06:52.320
<v Speaker 1>from the Internet and transfers it to your local area

0:06:52.360 --> 0:06:54.680
<v Speaker 1>network so that you can view it or interact with

0:06:54.680 --> 0:06:59.160
<v Speaker 1>it in whatever way. So that's the basic purpose of

0:06:59.200 --> 0:07:02.680
<v Speaker 1>a router, uh And it's you know, when you break

0:07:02.720 --> 0:07:04.479
<v Speaker 1>it down that way, it kind of it makes it

0:07:04.520 --> 0:07:07.040
<v Speaker 1>easier to understand why routers are important. Without a router,

0:07:07.560 --> 0:07:10.280
<v Speaker 1>you would not be able to have this this data

0:07:10.360 --> 0:07:14.240
<v Speaker 1>transfer between a larger network or or a computer on

0:07:14.320 --> 0:07:16.760
<v Speaker 1>another network and your computer you would just have You'd

0:07:16.800 --> 0:07:19.560
<v Speaker 1>be able to have communication through a local system, but

0:07:19.640 --> 0:07:22.760
<v Speaker 1>not through a global system. Unless you have a really

0:07:22.800 --> 0:07:27.400
<v Speaker 1>long cable. Yeah. That's especially important for the Internet because

0:07:27.400 --> 0:07:30.040
<v Speaker 1>as as you will remember, or at least as a

0:07:30.080 --> 0:07:33.360
<v Speaker 1>long time listeners will remember, Uh, traffic on the Internet

0:07:33.400 --> 0:07:39.760
<v Speaker 1>goes in little uh pieces or packets. They're actually called packets, um,

0:07:39.800 --> 0:07:43.840
<v Speaker 1>and they're sent uh redundantly. So you know, you might

0:07:43.880 --> 0:07:46.960
<v Speaker 1>take a file, uh say, an email and break it

0:07:47.000 --> 0:07:50.640
<v Speaker 1>down into a series of packets. Each of those has

0:07:50.720 --> 0:07:55.240
<v Speaker 1>some information that tells where it's going, UM, where it's

0:07:55.280 --> 0:07:58.040
<v Speaker 1>coming from, and what piece it is. It might be,

0:07:58.080 --> 0:08:02.480
<v Speaker 1>you know, piece three of packet three of forty, let's say, um,

0:08:02.520 --> 0:08:05.320
<v Speaker 1>so it tells uh the network where to send it

0:08:05.360 --> 0:08:07.120
<v Speaker 1>and how to reassemble it when it gets there. On

0:08:07.160 --> 0:08:11.040
<v Speaker 1>the other side, Well, the thing is, uh, it might say, okay, well,

0:08:11.160 --> 0:08:14.280
<v Speaker 1>I'm going from uh computer A to computer B, to

0:08:14.360 --> 0:08:17.680
<v Speaker 1>computer C to computer D. Well, all of a sudden,

0:08:17.760 --> 0:08:20.920
<v Speaker 1>there's a power failure at computer C, so it goes

0:08:20.960 --> 0:08:25.559
<v Speaker 1>from A to B. Oh it's stuck. Well, in the Internet, Uh,

0:08:25.600 --> 0:08:28.240
<v Speaker 1>it's set up where the packets can be sent and

0:08:28.320 --> 0:08:31.320
<v Speaker 1>re routed around computer C. So you might go to

0:08:31.320 --> 0:08:34.880
<v Speaker 1>computer F and then back to computer D. Because they

0:08:34.880 --> 0:08:37.880
<v Speaker 1>can be sent at multiple directions. At the same time,

0:08:37.920 --> 0:08:40.520
<v Speaker 1>and then you know with the idea that one set

0:08:40.600 --> 0:08:42.720
<v Speaker 1>of packets will be reassembled into the file on the

0:08:42.720 --> 0:08:46.600
<v Speaker 1>other end. And the router is crucial to making this happen. Yeah,

0:08:46.760 --> 0:08:50.360
<v Speaker 1>Routers have this thing called a routing table, and routing

0:08:50.400 --> 0:08:55.240
<v Speaker 1>table is essentially a guide saying this is where, this

0:08:55.280 --> 0:08:57.600
<v Speaker 1>is the direction you need to send packets in order

0:08:57.679 --> 0:09:00.760
<v Speaker 1>for information to come to go from to this machine

0:09:00.920 --> 0:09:03.880
<v Speaker 1>and get to that machine. So machine A and machine

0:09:03.880 --> 0:09:06.720
<v Speaker 1>beat will say, alright, So a routing table will in

0:09:06.800 --> 0:09:11.199
<v Speaker 1>general give the fastest uh route. Now, the fastest route

0:09:11.240 --> 0:09:15.120
<v Speaker 1>is not necessarily the shortest route, true, And it's the

0:09:15.160 --> 0:09:17.400
<v Speaker 1>same as if you live in a city. All right,

0:09:17.440 --> 0:09:19.680
<v Speaker 1>So let's say let's let's let's take the city as

0:09:19.720 --> 0:09:22.600
<v Speaker 1>a kind of a metaphor here. We're gonna look at

0:09:22.600 --> 0:09:25.000
<v Speaker 1>the city as an analog to the internet. It's not

0:09:25.679 --> 0:09:29.000
<v Speaker 1>it's not entirely analogous, but we're going to kind of

0:09:29.200 --> 0:09:31.600
<v Speaker 1>make some jumps here. So let's say you live in

0:09:31.640 --> 0:09:33.800
<v Speaker 1>a city and the city tends to have a lot

0:09:33.880 --> 0:09:37.679
<v Speaker 1>of traffic in it, and you may be at your

0:09:37.720 --> 0:09:39.600
<v Speaker 1>house and you want to go eat at a popular

0:09:39.640 --> 0:09:43.760
<v Speaker 1>restaurant that's across town. And so you know three different

0:09:43.800 --> 0:09:46.920
<v Speaker 1>ways of getting to the place across town. One of

0:09:46.920 --> 0:09:49.520
<v Speaker 1>them takes the least number of turns. It's it's the

0:09:49.559 --> 0:09:53.080
<v Speaker 1>most direct route, but it's also the most heavily traffic route.

0:09:53.600 --> 0:09:56.240
<v Speaker 1>So in other words, you could go that way and

0:09:56.360 --> 0:09:59.200
<v Speaker 1>you wouldn't have to turn as frequently, but because of

0:09:59.240 --> 0:10:02.520
<v Speaker 1>the the number of cars on that route, it will

0:10:02.559 --> 0:10:04.360
<v Speaker 1>actually take you longer to get there than if you

0:10:04.400 --> 0:10:07.960
<v Speaker 1>took a slightly more circuitous route that would have less

0:10:08.040 --> 0:10:09.960
<v Speaker 1>traffic on it. So in that case, you say, you

0:10:09.960 --> 0:10:12.440
<v Speaker 1>know what, I know that this is the direct path,

0:10:12.559 --> 0:10:14.040
<v Speaker 1>but I'm going to take this more out of the

0:10:14.040 --> 0:10:17.400
<v Speaker 1>way path. This it's it's a shortcut in time, but

0:10:17.520 --> 0:10:20.040
<v Speaker 1>not in distance. And the same thing is true on

0:10:20.040 --> 0:10:22.280
<v Speaker 1>the internet. You might be able to find a route

0:10:22.320 --> 0:10:26.080
<v Speaker 1>to push traffic through that's going to be faster, even

0:10:26.120 --> 0:10:29.120
<v Speaker 1>though it's not as direct. By the way, if you

0:10:29.160 --> 0:10:31.600
<v Speaker 1>happen to live in Los Angeles, I understand that this

0:10:31.640 --> 0:10:34.880
<v Speaker 1>is a sport that in Los Angeles, if you have

0:10:34.920 --> 0:10:36.960
<v Speaker 1>a group of people and you have all decided to

0:10:37.000 --> 0:10:40.719
<v Speaker 1>go someplace, the first hour of your travel time will

0:10:40.720 --> 0:10:43.760
<v Speaker 1>actually be taken up spending time talking about the best

0:10:43.800 --> 0:10:47.640
<v Speaker 1>way to get to where you're going. Okay, yeah, very

0:10:47.640 --> 0:10:51.280
<v Speaker 1>little driving in LA so well that's it's. What's required

0:10:51.320 --> 0:10:54.000
<v Speaker 1>is that you and at least one other person each

0:10:54.120 --> 0:10:56.560
<v Speaker 1>in their own vehicles, have to be going to a

0:10:56.720 --> 0:11:00.240
<v Speaker 1>specific place, leaving from the same location. And at that

0:11:00.320 --> 0:11:03.720
<v Speaker 1>point you have launched into the game where then you

0:11:03.760 --> 0:11:05.400
<v Speaker 1>say no, no, no, you don't want to do that.

0:11:05.400 --> 0:11:06.880
<v Speaker 1>That's going to take you on the four oh five

0:11:07.080 --> 0:11:10.600
<v Speaker 1>And haven't you heard of Carmageddon? And um so, yeah,

0:11:10.720 --> 0:11:12.960
<v Speaker 1>it's the same sort of thing. Now. Granted, if if

0:11:13.040 --> 0:11:16.480
<v Speaker 1>the city were empty, then the direct route would be

0:11:16.520 --> 0:11:19.599
<v Speaker 1>the shortest, but the city is never empty because the

0:11:19.720 --> 0:11:23.440
<v Speaker 1>zombie apocalypse hasn't happened yet, at least at the time

0:11:23.480 --> 0:11:27.080
<v Speaker 1>of the recording of this podcast. Yes so, and by

0:11:27.120 --> 0:11:30.320
<v Speaker 1>the way, if by the zombie apocalypse has happened since

0:11:30.320 --> 0:11:32.400
<v Speaker 1>we record this podcast, I would like to have a

0:11:32.400 --> 0:11:35.320
<v Speaker 1>shout out to all of our new listeners with BRAT.

0:11:37.400 --> 0:11:41.880
<v Speaker 1>We're great with the zombie demographic. Oh I'm a little

0:11:41.880 --> 0:11:45.200
<v Speaker 1>loopy today, Yeah you know, I hadn't noticed. Yeah, so anyway,

0:11:45.240 --> 0:11:48.640
<v Speaker 1>The routing table is this list of essentially rules that

0:11:48.679 --> 0:11:52.400
<v Speaker 1>the router follows in order to send packets across the network.

0:11:52.400 --> 0:11:56.520
<v Speaker 1>And you might say, well, that seems pretty um stiff

0:11:56.640 --> 0:12:00.120
<v Speaker 1>and and and inflexible. What happens when things change, Well,

0:12:00.440 --> 0:12:04.160
<v Speaker 1>routing tables are not static. They are dynamic. They change

0:12:04.640 --> 0:12:07.840
<v Speaker 1>all the time. And what's happening is routers are actually

0:12:07.840 --> 0:12:12.560
<v Speaker 1>communicating with each other across the Internet constantly updating this

0:12:12.679 --> 0:12:16.120
<v Speaker 1>information and changing it so that the most uh, the

0:12:16.160 --> 0:12:21.680
<v Speaker 1>most efficient route is constantly being adjusted. And they're doing

0:12:21.679 --> 0:12:25.000
<v Speaker 1>this through various protocols. Routing Information Protocol or r I

0:12:25.080 --> 0:12:29.520
<v Speaker 1>p RIP that would be the one of the common

0:12:29.600 --> 0:12:32.800
<v Speaker 1>protocols used. Another one is the Open Shortest Path First

0:12:32.960 --> 0:12:38.480
<v Speaker 1>or OSPF protocol. These protocols are what routers use in

0:12:38.600 --> 0:12:41.640
<v Speaker 1>order to update these routing tables so that data will

0:12:41.640 --> 0:12:45.280
<v Speaker 1>co go across the network, across the Internet in the

0:12:45.320 --> 0:12:49.120
<v Speaker 1>most efficient way possible, the way that's got the best

0:12:49.120 --> 0:12:51.200
<v Speaker 1>guarantee that your information is going to get to where

0:12:51.200 --> 0:12:54.760
<v Speaker 1>it needs to be. And each packet that Chris was

0:12:54.760 --> 0:12:57.680
<v Speaker 1>talking about earlier has data in it that allows it

0:12:57.760 --> 0:13:02.559
<v Speaker 1>to um well, allows it to the system to keep

0:13:02.600 --> 0:13:04.560
<v Speaker 1>track of it. So let's say that you've sent a

0:13:04.600 --> 0:13:06.960
<v Speaker 1>file like let's say I'm sending a file to Chris

0:13:07.200 --> 0:13:09.400
<v Speaker 1>and Chris is on one network and I'm on another network,

0:13:10.240 --> 0:13:13.480
<v Speaker 1>and uh, some of my packets don't get through. Well,

0:13:13.520 --> 0:13:16.679
<v Speaker 1>the system keeps track of that. The what will happen

0:13:16.720 --> 0:13:18.920
<v Speaker 1>is the information will come back to my computer and

0:13:18.960 --> 0:13:23.440
<v Speaker 1>it will say, hey, packets three, seven, and twelve out

0:13:23.480 --> 0:13:25.520
<v Speaker 1>of the forty that you sent never made it to

0:13:25.600 --> 0:13:29.000
<v Speaker 1>Chris's machine. Then my machine will automatically re send those

0:13:29.000 --> 0:13:33.360
<v Speaker 1>packets so that they will hopefully get to Chris's machine. Now, granted,

0:13:33.400 --> 0:13:35.640
<v Speaker 1>all this is happening at near the speed of light,

0:13:35.760 --> 0:13:39.520
<v Speaker 1>so you don't really notice the delay unless something's really

0:13:39.559 --> 0:13:43.000
<v Speaker 1>really bad has happened. Um. And so this is all

0:13:43.040 --> 0:13:45.640
<v Speaker 1>happening in the blink of an eye, but it's happening

0:13:45.640 --> 0:13:51.559
<v Speaker 1>over and over and over across the Internet, right, um

0:13:51.640 --> 0:13:53.880
<v Speaker 1>and and yes it's um just to go back to

0:13:53.880 --> 0:13:57.920
<v Speaker 1>protocols to the protocols are basically, uh, languages that the

0:13:58.000 --> 0:14:01.480
<v Speaker 1>routers used to speak to one another. Um. It's it

0:14:01.600 --> 0:14:06.880
<v Speaker 1>enables people multiple manufacturers to make devices that will communicate

0:14:06.920 --> 0:14:10.120
<v Speaker 1>with one another and be interoperable, which is you know,

0:14:10.600 --> 0:14:13.920
<v Speaker 1>we talked about that actually on our podcast about how

0:14:14.160 --> 0:14:16.440
<v Speaker 1>the Internet works, and we mentioned on some of the others.

0:14:16.440 --> 0:14:19.280
<v Speaker 1>I think we probably did on IPv six that, uh,

0:14:19.320 --> 0:14:21.720
<v Speaker 1>there are certain protocols that allow MC to talk to

0:14:21.800 --> 0:14:23.920
<v Speaker 1>a Linux box and the Linux box to talk to

0:14:23.960 --> 0:14:26.600
<v Speaker 1>a PC and etcetera. Right, they're all they're all using

0:14:26.640 --> 0:14:32.880
<v Speaker 1>the computer equivalent of Esperanto. Yes, no, anyway, Yeah, that's

0:14:32.920 --> 0:14:35.560
<v Speaker 1>that's what that's what our protocol is. And route routers

0:14:35.600 --> 0:14:38.520
<v Speaker 1>do have those, uh, protocols that are specific to routers,

0:14:38.520 --> 0:14:40.600
<v Speaker 1>and that that does help them balance the load somewhat

0:14:40.640 --> 0:14:42.680
<v Speaker 1>on the Internet. Yeah, we should should say, I guess

0:14:42.680 --> 0:14:45.440
<v Speaker 1>that a router really is a very specific computer. It's

0:14:45.440 --> 0:14:47.280
<v Speaker 1>not just this box that you buy and you know

0:14:47.280 --> 0:14:49.240
<v Speaker 1>it's got lights on it and when it's lit up,

0:14:49.240 --> 0:14:51.320
<v Speaker 1>you know that the information is going through it is

0:14:51.400 --> 0:14:55.920
<v Speaker 1>actually a very specific type of computer. Yeah, very specialized device.

0:14:55.960 --> 0:14:57.480
<v Speaker 1>And and a lot of the routers, like the home

0:14:57.560 --> 0:15:00.200
<v Speaker 1>routers that you purchase for your your home network, whether

0:15:00.240 --> 0:15:03.760
<v Speaker 1>it's wireless or wired, also tend to act as a switch.

0:15:04.240 --> 0:15:06.640
<v Speaker 1>And what by by that, I mean that it allows

0:15:06.680 --> 0:15:10.440
<v Speaker 1>you to have your computers talk to one another. So

0:15:10.480 --> 0:15:13.040
<v Speaker 1>if you have multiple computers at your house, you can

0:15:13.040 --> 0:15:15.880
<v Speaker 1>send files from one machine to another machine without having

0:15:15.920 --> 0:15:18.040
<v Speaker 1>to set up like some weird email thing or whatever,

0:15:18.080 --> 0:15:20.400
<v Speaker 1>you can actually send it directly through your home network

0:15:20.680 --> 0:15:23.280
<v Speaker 1>because your router also can be a switch. It's not

0:15:23.400 --> 0:15:27.040
<v Speaker 1>just a router that sends information from your network to

0:15:27.120 --> 0:15:30.720
<v Speaker 1>the Internet and back. Um. Also, when we were talking

0:15:30.760 --> 0:15:33.960
<v Speaker 1>about information going across the network and figuring out the

0:15:33.960 --> 0:15:37.280
<v Speaker 1>most efficient way, in the sense of routers, what they

0:15:37.960 --> 0:15:43.440
<v Speaker 1>do is they calculate the cost of a of any

0:15:43.520 --> 0:15:47.960
<v Speaker 1>particular data transmission, and cost does not mean dollars. It

0:15:48.000 --> 0:15:52.360
<v Speaker 1>means hops, alright, So when a router sends information across

0:15:52.400 --> 0:15:55.200
<v Speaker 1>the network, information may go from one router to another

0:15:55.280 --> 0:15:57.720
<v Speaker 1>router to another router until it finally gets to wherever

0:15:57.760 --> 0:16:01.280
<v Speaker 1>it's going. All right, Each time that information goes from

0:16:01.320 --> 0:16:05.600
<v Speaker 1>one route or to another, that's called a hop, right now. Protocols,

0:16:05.640 --> 0:16:09.600
<v Speaker 1>certain protocols have a limited number of hops that are

0:16:09.680 --> 0:16:13.760
<v Speaker 1>built into uh any sort of data transference, and that

0:16:13.800 --> 0:16:17.120
<v Speaker 1>information is stored in the data packet. Okay, So it's

0:16:17.120 --> 0:16:20.400
<v Speaker 1>almost like I'm passing a note in class, and the

0:16:20.560 --> 0:16:23.960
<v Speaker 1>note can only pass through three other people before it

0:16:24.000 --> 0:16:26.240
<v Speaker 1>gets to my destination. It's one of them, the teacher.

0:16:26.880 --> 0:16:31.920
<v Speaker 1>The teacher accesses the the packet of information it gets discarded,

0:16:32.120 --> 0:16:35.880
<v Speaker 1>which is very much like what happens on the internet. Actually, so,

0:16:35.880 --> 0:16:38.680
<v Speaker 1>so let's say that again. But now we're talking about

0:16:38.680 --> 0:16:42.640
<v Speaker 1>a classroom. So Chris is sitting across the class from

0:16:42.680 --> 0:16:45.160
<v Speaker 1>from me. I'm on one side, he's on the other side.

0:16:45.440 --> 0:16:48.760
<v Speaker 1>I want to pass him a note that says something like, uh,

0:16:48.880 --> 0:16:51.120
<v Speaker 1>I don't know the didn't the teacher wear that same

0:16:51.160 --> 0:16:54.040
<v Speaker 1>outfit yesterday? And so I'm trying to send the the

0:16:54.280 --> 0:16:57.440
<v Speaker 1>note across the class and it can only pass through

0:16:57.520 --> 0:17:01.320
<v Speaker 1>three other hands up before it hits Chris. If it

0:17:01.360 --> 0:17:04.480
<v Speaker 1>passes through more than that, then whoever the fourth person

0:17:04.560 --> 0:17:07.040
<v Speaker 1>is is like, this is not worthwhile and just tosses

0:17:07.080 --> 0:17:10.240
<v Speaker 1>the note away. The same thing is happening with hop

0:17:10.320 --> 0:17:13.120
<v Speaker 1>counts if I send a packet of information. If I'm

0:17:13.119 --> 0:17:16.000
<v Speaker 1>sending a file to Chris and it's going across the Internet,

0:17:16.040 --> 0:17:18.399
<v Speaker 1>there's a certain number of hops that packet will go

0:17:18.480 --> 0:17:21.600
<v Speaker 1>through before it hits the maximum number of hop count.

0:17:21.760 --> 0:17:23.680
<v Speaker 1>Now that does not mean that the packet just automatically

0:17:23.720 --> 0:17:26.119
<v Speaker 1>gets thrown away. It means that the system says, you

0:17:26.160 --> 0:17:28.720
<v Speaker 1>know what, this packet has gone through this kind of

0:17:28.840 --> 0:17:32.000
<v Speaker 1>serpentine pathway in order to get to where it's going.

0:17:32.320 --> 0:17:35.199
<v Speaker 1>It's not getting there efficiently. Chances are this packet has

0:17:35.280 --> 0:17:39.639
<v Speaker 1>already made it to the destination through a fewer number

0:17:39.680 --> 0:17:41.679
<v Speaker 1>of hops. So I'm just going to toss the packet

0:17:41.680 --> 0:17:46.240
<v Speaker 1>aside because otherwise, because the Internet is a redundant system,

0:17:46.320 --> 0:17:49.040
<v Speaker 1>and because it's meant to be robust, and it's meant

0:17:49.040 --> 0:17:52.160
<v Speaker 1>to get a packet of information to the destination through

0:17:52.200 --> 0:17:56.440
<v Speaker 1>whatever means possible within the parameters of the Internet. If

0:17:56.480 --> 0:18:00.280
<v Speaker 1>you didn't have these sort of uh discards them is

0:18:00.280 --> 0:18:05.040
<v Speaker 1>put into place, the Internet would become overrun with packets. Yeah,

0:18:05.080 --> 0:18:07.280
<v Speaker 1>because you know, if I'm sending that file to Chris

0:18:07.320 --> 0:18:10.600
<v Speaker 1>and there's these duplicate packets going across the network, what

0:18:10.760 --> 0:18:13.679
<v Speaker 1>happens when one packet gets to the destination and the

0:18:13.680 --> 0:18:16.119
<v Speaker 1>other packets are still out there trying to trying to

0:18:16.119 --> 0:18:18.560
<v Speaker 1>get to the destination. You're starting to clog up the

0:18:18.600 --> 0:18:22.680
<v Speaker 1>Internet with all of this data. So these these fail

0:18:22.760 --> 0:18:26.320
<v Speaker 1>safes are in place in order to prevent the Internet

0:18:26.400 --> 0:18:30.199
<v Speaker 1>from just bogging down with too much data. And they

0:18:30.200 --> 0:18:32.680
<v Speaker 1>didn't have to buy a like a digital router and

0:18:32.760 --> 0:18:35.520
<v Speaker 1>go in and yeah, we've got we've got the routers,

0:18:35.560 --> 0:18:39.480
<v Speaker 1>but not the routers router routers. I had to call

0:18:39.560 --> 0:18:41.880
<v Speaker 1>them once it was did not go well, No, it's

0:18:42.040 --> 0:18:45.800
<v Speaker 1>never anyway. Um. So in order to make all this work,

0:18:45.920 --> 0:18:49.160
<v Speaker 1>in addition to your router and your network, you also

0:18:49.200 --> 0:18:52.240
<v Speaker 1>have to have an address, a unique address for each

0:18:52.240 --> 0:18:54.840
<v Speaker 1>item on the network. And this we've talked about in

0:18:55.119 --> 0:18:58.119
<v Speaker 1>the I p V four versus I p V six podcast.

0:18:59.200 --> 0:19:03.680
<v Speaker 1>Ideally you would have every single device that connects to

0:19:03.680 --> 0:19:08.160
<v Speaker 1>the Internet would have its own unique address, so that

0:19:08.640 --> 0:19:11.679
<v Speaker 1>whenever I want to send something to another device or

0:19:11.760 --> 0:19:14.879
<v Speaker 1>receive information from another device, it would always go to

0:19:14.960 --> 0:19:17.680
<v Speaker 1>the same address. And that way, it's just it's just efficient.

0:19:17.720 --> 0:19:21.040
<v Speaker 1>It's a clean, efficient system. But we don't have enough

0:19:21.160 --> 0:19:25.560
<v Speaker 1>addresses to do that, right. But each item and you

0:19:25.600 --> 0:19:27.640
<v Speaker 1>may have actually seen this when you're going into your

0:19:28.040 --> 0:19:31.800
<v Speaker 1>computer or you know, other devices like tablets and smartphones

0:19:31.800 --> 0:19:36.120
<v Speaker 1>that use Internet networks, or video game systems, video game systems, uh,

0:19:36.200 --> 0:19:39.679
<v Speaker 1>set top boxes, TVs. There's a lot of different devices

0:19:39.720 --> 0:19:42.480
<v Speaker 1>that do it now, which is again part of the problem. Yeah,

0:19:42.520 --> 0:19:45.000
<v Speaker 1>that this is called a MAC address. It's known as

0:19:45.240 --> 0:19:49.440
<v Speaker 1>Media Access control and it doesn't look like well, actually,

0:19:49.560 --> 0:19:53.240
<v Speaker 1>it kind of resembles an IP address because it has

0:19:53.240 --> 0:19:57.760
<v Speaker 1>a series of letters and numbers separated by by colon's

0:19:58.480 --> 0:20:00.920
<v Speaker 1>and that this is how you can identify I. Um,

0:20:00.960 --> 0:20:04.520
<v Speaker 1>you know, say you have been foolish and have left

0:20:04.600 --> 0:20:11.160
<v Speaker 1>your wireless network open to the public, and you have

0:20:11.400 --> 0:20:15.359
<v Speaker 1>let's say a computer and a tablet and wait a minute,

0:20:15.359 --> 0:20:19.359
<v Speaker 1>there are three things on your network. Well, then you

0:20:19.359 --> 0:20:21.800
<v Speaker 1>can look at the MAC address on your computer, and

0:20:21.800 --> 0:20:23.480
<v Speaker 1>you can look at the MAC address and your tablet

0:20:24.280 --> 0:20:27.760
<v Speaker 1>and UH by process of elimination, figure out what the

0:20:27.800 --> 0:20:31.800
<v Speaker 1>other device is and maybe even get an idea. If

0:20:31.840 --> 0:20:37.879
<v Speaker 1>you can access the uh um the routers information page,

0:20:37.920 --> 0:20:40.399
<v Speaker 1>you can you can see what what's going on, how

0:20:40.480 --> 0:20:43.359
<v Speaker 1>much traffic it's using, and hopefully shut it down. You

0:20:43.359 --> 0:20:46.639
<v Speaker 1>can even on on some uh probably on most of them,

0:20:46.680 --> 0:20:49.960
<v Speaker 1>I would guess. I just don't want to be absolute um,

0:20:50.000 --> 0:20:52.880
<v Speaker 1>you know, restricted to certain Mac addresses, so you can

0:20:52.960 --> 0:20:55.159
<v Speaker 1>you can actually add you can on mind on the

0:20:56.119 --> 0:20:58.960
<v Speaker 1>device I have at home. You can say, you know,

0:20:59.040 --> 0:21:02.679
<v Speaker 1>I'm adding this tablet, I'm adding this game console, I'm

0:21:02.720 --> 0:21:06.879
<v Speaker 1>adding this uh smartphone, I actually use WiFi calling on

0:21:06.920 --> 0:21:09.280
<v Speaker 1>my smartphone, you know, and things like that, and say, okay,

0:21:09.440 --> 0:21:13.200
<v Speaker 1>I'm only allowing MAC addresses that I know to join

0:21:13.280 --> 0:21:17.160
<v Speaker 1>this network. But Basically, this is a way for um,

0:21:17.200 --> 0:21:20.840
<v Speaker 1>you know, local networks to identify the devices and send

0:21:20.960 --> 0:21:22.960
<v Speaker 1>the packets that go to that device, so they know,

0:21:23.480 --> 0:21:26.080
<v Speaker 1>um that if you are reading how Stuff Works dot

0:21:26.080 --> 0:21:31.840
<v Speaker 1>Com and your spouse is looking at a news network

0:21:32.359 --> 0:21:34.359
<v Speaker 1>and you know you don't get the packets mixed up.

0:21:34.359 --> 0:21:36.440
<v Speaker 1>It says, oh, well, these belong to this address, these

0:21:36.480 --> 0:21:38.320
<v Speaker 1>belong to that address, and I'm going to be the

0:21:38.320 --> 0:21:42.440
<v Speaker 1>traffic cop and send the right packets to the right place, right. Yeah.

0:21:42.440 --> 0:21:45.440
<v Speaker 1>This this kind of ties into network address translation, which

0:21:45.440 --> 0:21:47.960
<v Speaker 1>I referred to at the beginning of the podcast. We've

0:21:47.960 --> 0:21:49.800
<v Speaker 1>also talked about that in the I p V four

0:21:49.920 --> 0:21:51.760
<v Speaker 1>versus I p V six. Yes, it's one of the

0:21:51.760 --> 0:21:54.960
<v Speaker 1>ways to address the problem of having more devices in

0:21:55.000 --> 0:21:59.400
<v Speaker 1>the world than we have available IP addresses for those

0:21:59.400 --> 0:22:03.119
<v Speaker 1>devices to connect to the Internet. Now, for information to

0:22:03.119 --> 0:22:05.840
<v Speaker 1>travel across the Internet, it means that you have to

0:22:05.920 --> 0:22:11.199
<v Speaker 1>have an Internet Protocol address. This allows the information to

0:22:11.359 --> 0:22:14.760
<v Speaker 1>travel across it allows it allows other computers to find you,

0:22:15.000 --> 0:22:18.640
<v Speaker 1>and allows your computer to send information to other computers. Uh.

0:22:18.680 --> 0:22:20.720
<v Speaker 1>Without the IP addresses, you of course would have no

0:22:20.800 --> 0:22:24.040
<v Speaker 1>way of knowing how to get information from one machine

0:22:24.080 --> 0:22:26.680
<v Speaker 1>to another. It's kind of like in a sense, it's

0:22:26.720 --> 0:22:29.080
<v Speaker 1>kind of like a physical address or phone number. If

0:22:29.119 --> 0:22:31.040
<v Speaker 1>we didn't have phone numbers, if it was all a

0:22:31.080 --> 0:22:33.000
<v Speaker 1>party line, you would just have to pick up the

0:22:33.000 --> 0:22:35.720
<v Speaker 1>phone and hope that whomever you're trying to contact is

0:22:35.800 --> 0:22:38.520
<v Speaker 1>also on the phone at that time, and everyone else

0:22:38.520 --> 0:22:40.320
<v Speaker 1>will be able to hear your conversation at the same time.

0:22:40.359 --> 0:22:43.800
<v Speaker 1>And but in just curious, have we ever talked about

0:22:43.800 --> 0:22:46.400
<v Speaker 1>party lines? I don't think, so that might be fun.

0:22:46.440 --> 0:22:48.240
<v Speaker 1>Then we can add that to the to do list.

0:22:48.560 --> 0:22:52.680
<v Speaker 1>So the network address translation, this is a layer that,

0:22:52.920 --> 0:22:55.720
<v Speaker 1>uh that could be very useful in this sense. You

0:22:55.720 --> 0:22:57.960
<v Speaker 1>would have a router that would have a number of

0:22:58.040 --> 0:23:01.520
<v Speaker 1>static IP addresses, or it possibly would have a number

0:23:01.520 --> 0:23:04.639
<v Speaker 1>of addresses assigned to it by the whatever your Internet

0:23:04.680 --> 0:23:10.639
<v Speaker 1>service provider is. Your devices would not have static IP addresses.

0:23:10.680 --> 0:23:15.159
<v Speaker 1>They would have like some non unique IP address and

0:23:15.240 --> 0:23:18.760
<v Speaker 1>dynamically assigned and and and because they are non unique,

0:23:19.119 --> 0:23:22.520
<v Speaker 1>that means you can't just automatically tag into the Internet

0:23:22.560 --> 0:23:26.080
<v Speaker 1>and send stuff because if it's a non unique address,

0:23:26.160 --> 0:23:28.280
<v Speaker 1>I mean some other devices out there on the Internet

0:23:28.320 --> 0:23:31.600
<v Speaker 1>may also have that same address, So anything you request

0:23:31.640 --> 0:23:34.040
<v Speaker 1>would be sent to all of them. So what happens

0:23:34.080 --> 0:23:37.400
<v Speaker 1>is your router acts as kind of a postmaster. You

0:23:37.480 --> 0:23:41.080
<v Speaker 1>have this non unique address. You send information to the

0:23:41.480 --> 0:23:43.800
<v Speaker 1>you're trying to get, uh, let's say again a website.

0:23:43.960 --> 0:23:47.480
<v Speaker 1>I'm trying to visit a website. Uh. That request goes

0:23:47.480 --> 0:23:50.520
<v Speaker 1>through to my router. My router then replaces my non

0:23:50.640 --> 0:23:55.480
<v Speaker 1>unique address with a unique static IP address and keeps

0:23:55.560 --> 0:23:59.280
<v Speaker 1>track of that relationship within the routing table. When it's

0:23:59.280 --> 0:24:03.040
<v Speaker 1>own pro re calls, sends that request out to the internet.

0:24:03.240 --> 0:24:05.720
<v Speaker 1>It eventually gets to the server that I want. The

0:24:05.760 --> 0:24:08.639
<v Speaker 1>information comes back to the router. The routers says, all right,

0:24:08.840 --> 0:24:13.440
<v Speaker 1>this information is meant for static IP address whatever. Now

0:24:13.440 --> 0:24:16.080
<v Speaker 1>it has to refer to its table and see which

0:24:16.200 --> 0:24:18.760
<v Speaker 1>of your devices on your home network, your local area

0:24:18.800 --> 0:24:23.639
<v Speaker 1>network has temporarily been assigned that static address. It then

0:24:23.720 --> 0:24:25.800
<v Speaker 1>sends the information to you. If if you are no

0:24:25.840 --> 0:24:29.479
<v Speaker 1>longer part of that network, or if it can identify it,

0:24:29.480 --> 0:24:34.480
<v Speaker 1>it gets dumped. It dumps that information so it goes nowhere. Um. Now,

0:24:34.800 --> 0:24:38.280
<v Speaker 1>this is one of the things that kind of it

0:24:39.119 --> 0:24:42.040
<v Speaker 1>depending on the type of engineer, it can really irritate

0:24:42.080 --> 0:24:45.680
<v Speaker 1>engineers because it's a less efficient system and this is

0:24:45.720 --> 0:24:49.520
<v Speaker 1>also one of the issues with gaming routers we talked about.

0:24:49.800 --> 0:24:51.919
<v Speaker 1>You know, the request asked about what kind of routers

0:24:51.920 --> 0:24:56.399
<v Speaker 1>are best for gaming. Well, because of the network address translation,

0:24:56.520 --> 0:25:01.440
<v Speaker 1>this can slow down data trans mission a little bit.

0:25:01.480 --> 0:25:04.480
<v Speaker 1>I mean, there can also be some compatibility issues, um,

0:25:04.760 --> 0:25:08.600
<v Speaker 1>especially if the router has to change these the IP

0:25:08.760 --> 0:25:11.119
<v Speaker 1>address for whatever the device is. Like, if you've got

0:25:11.119 --> 0:25:12.840
<v Speaker 1>a lot of devices that are connecting to this router,

0:25:13.000 --> 0:25:16.600
<v Speaker 1>there could be some complications and complications when you're gaming.

0:25:16.840 --> 0:25:19.639
<v Speaker 1>That's a bad thing because it's going to affect how

0:25:19.760 --> 0:25:22.560
<v Speaker 1>fast that information is traveling to whichever device you're using

0:25:22.600 --> 0:25:26.600
<v Speaker 1>the game. It's complicated. Yeah, well that can that can

0:25:26.680 --> 0:25:29.240
<v Speaker 1>mean that you will get lag in the game you're playing.

0:25:29.320 --> 0:25:32.359
<v Speaker 1>It means that you might get artifacts. Uh, the game

0:25:32.400 --> 0:25:34.560
<v Speaker 1>will not play as well as you would want it to.

0:25:35.320 --> 0:25:40.720
<v Speaker 1>So any any device that's using that you're that's one

0:25:40.720 --> 0:25:42.880
<v Speaker 1>of the things you gotta look at, like, well, how

0:25:43.000 --> 0:25:48.640
<v Speaker 1>how well rated is this router for that particular function. Um.

0:25:48.680 --> 0:25:51.959
<v Speaker 1>Also depending on well, if you are a serious gamer,

0:25:52.000 --> 0:25:56.399
<v Speaker 1>you probably you probably want a wired router. Uh. A

0:25:56.400 --> 0:26:01.040
<v Speaker 1>lot of the wireless routers also have wired connections to them. Yeah,

0:26:01.119 --> 0:26:03.960
<v Speaker 1>so you probably want a wired connection, and the reason

0:26:04.000 --> 0:26:07.280
<v Speaker 1>for that is that it's more reliable than wireless. You

0:26:07.320 --> 0:26:10.439
<v Speaker 1>are less likely to have interference. Uh, you're not going

0:26:10.480 --> 0:26:12.720
<v Speaker 1>to find a dead spot. Like you know, if you

0:26:12.760 --> 0:26:15.560
<v Speaker 1>have your wireless network set up in one room and

0:26:15.600 --> 0:26:18.520
<v Speaker 1>you tend to game in a different room and uh,

0:26:18.560 --> 0:26:23.240
<v Speaker 1>and there are certain materials in your walls, it may

0:26:23.320 --> 0:26:25.080
<v Speaker 1>end up blocking some of the signal, which means that

0:26:25.119 --> 0:26:26.960
<v Speaker 1>you may not have a clear signal and that will

0:26:26.960 --> 0:26:30.399
<v Speaker 1>affect your gaming. So a wired connection tends to be

0:26:30.480 --> 0:26:34.119
<v Speaker 1>best if you want to go wireless. UH, the IN

0:26:34.480 --> 0:26:37.600
<v Speaker 1>protocol tends to be the best. It's the fastest, and

0:26:37.640 --> 0:26:41.400
<v Speaker 1>it has a really good penetration as far as various

0:26:41.520 --> 0:26:44.040
<v Speaker 1>materials goes. So if you have a wireless or other

0:26:44.080 --> 0:26:47.000
<v Speaker 1>set up, it's a it's a pretty good bet. G

0:26:47.480 --> 0:26:50.040
<v Speaker 1>is the next step. I would go with either INN

0:26:50.119 --> 0:26:52.320
<v Speaker 1>or G preferably. And now you have to make sure

0:26:52.320 --> 0:26:56.920
<v Speaker 1>that whatever devices you're using are compatible with that particular protocol. Yes,

0:26:57.000 --> 0:27:00.080
<v Speaker 1>that's the eight O, two dot eleven. Yes, proto a

0:27:00.119 --> 0:27:04.040
<v Speaker 1>call with with the various flavors A, B, G and yeah.

0:27:04.320 --> 0:27:06.359
<v Speaker 1>And so if you have a if you have a

0:27:06.359 --> 0:27:11.080
<v Speaker 1>device that is running that it can accept G. I mean,

0:27:11.119 --> 0:27:13.440
<v Speaker 1>these are all different kinds of radio frequencies, but it

0:27:13.800 --> 0:27:18.640
<v Speaker 1>is designed for a G frequency then G rated. Yeah,

0:27:19.080 --> 0:27:21.320
<v Speaker 1>and you have an N router, it's not gonna work.

0:27:21.480 --> 0:27:23.919
<v Speaker 1>They are not compatible. You have to have one that

0:27:23.960 --> 0:27:26.720
<v Speaker 1>can do I mean, they're great. There are plenty of

0:27:26.760 --> 0:27:30.280
<v Speaker 1>routers out there that will do multiple frequencies, and there

0:27:30.280 --> 0:27:35.159
<v Speaker 1>are plenty of of UH wireless chips out there that

0:27:35.200 --> 0:27:37.760
<v Speaker 1>can do multiple frequencies as well, But you want to

0:27:37.800 --> 0:27:40.120
<v Speaker 1>make sure that you do have that compatibility in there

0:27:40.200 --> 0:27:42.840
<v Speaker 1>or else. You know, you might have the fastest connection

0:27:43.960 --> 0:27:47.000
<v Speaker 1>with the router possible, but your device is not compatible.

0:27:47.040 --> 0:27:50.959
<v Speaker 1>Also keep in mind this is also very heavily dependent

0:27:51.040 --> 0:27:55.560
<v Speaker 1>upon what your internet service provider plan is, because if

0:27:55.600 --> 0:27:58.560
<v Speaker 1>you're you can have the if you have the fastest router,

0:27:58.680 --> 0:28:00.760
<v Speaker 1>and you think of it like a doorway, it could

0:28:00.760 --> 0:28:03.520
<v Speaker 1>be a really really wide doorway, but the path is

0:28:03.600 --> 0:28:06.959
<v Speaker 1>really narrow once you open the door, it doesn't help you.

0:28:06.960 --> 0:28:09.399
<v Speaker 1>You have to have that broadband connection with a really

0:28:09.440 --> 0:28:12.160
<v Speaker 1>good data transfer rate for the router to even make

0:28:12.160 --> 0:28:15.040
<v Speaker 1>a difference. Um, if you don't have that high speed

0:28:15.040 --> 0:28:19.040
<v Speaker 1>internet connection, if your cable modem or or however you're

0:28:19.080 --> 0:28:23.080
<v Speaker 1>getting your your internet. If that is a bottleneck, the

0:28:23.160 --> 0:28:26.280
<v Speaker 1>router is not gonna help. You have to have that too. Yeah.

0:28:26.359 --> 0:28:28.359
<v Speaker 1>Keep in mind too that if your I s P

0:28:28.800 --> 0:28:32.200
<v Speaker 1>caps data, you might keep an eye on that. Yeah,

0:28:32.240 --> 0:28:34.560
<v Speaker 1>I mean, depending on what you're doing, it may not

0:28:34.600 --> 0:28:37.720
<v Speaker 1>make a difference. Most people never reach their I s

0:28:37.800 --> 0:28:40.640
<v Speaker 1>P S data cap, although that's that's changing as people

0:28:40.640 --> 0:28:44.440
<v Speaker 1>are getting more into like consuming streaming video. You know.

0:28:44.600 --> 0:28:48.400
<v Speaker 1>So if you are watching some streaming video service and

0:28:48.480 --> 0:28:51.680
<v Speaker 1>you're perhaps you have it on a couple of different televisions.

0:28:51.680 --> 0:28:53.400
<v Speaker 1>I mean it's not unusual now. You might have a

0:28:53.520 --> 0:28:56.640
<v Speaker 1>Roku box on one machine one television. You might have

0:28:56.680 --> 0:28:59.600
<v Speaker 1>a an Xbox three six yr ps three on another one.

0:28:59.840 --> 0:29:03.680
<v Speaker 1>You could potentially have five or six different televisions all

0:29:03.720 --> 0:29:06.800
<v Speaker 1>consuming streaming video. That's gonna that's gonna cause a pretty

0:29:06.840 --> 0:29:09.000
<v Speaker 1>big bottleneck too. You've gotta have a really good Internet

0:29:09.040 --> 0:29:11.640
<v Speaker 1>connection and a decent router for that to work. It's

0:29:11.680 --> 0:29:16.360
<v Speaker 1>not impossible. Um, it's impossible with my setup, but because

0:29:16.400 --> 0:29:18.880
<v Speaker 1>I have a I have a much slower home network. Uh.

0:29:18.920 --> 0:29:22.480
<v Speaker 1>But yeah, if you don't, um, yeah, that's that's possible,

0:29:22.520 --> 0:29:24.960
<v Speaker 1>and then that could very quickly run up against a

0:29:25.280 --> 0:29:29.720
<v Speaker 1>data cap right. Uh, did you want to touch on

0:29:29.840 --> 0:29:32.080
<v Speaker 1>There's one one issue I thought it might be interesting

0:29:32.120 --> 0:29:35.120
<v Speaker 1>to touch on. UM. That's in the routers article on

0:29:35.120 --> 0:29:38.560
<v Speaker 1>how stuff works dot com. And that's what happens when

0:29:38.560 --> 0:29:44.280
<v Speaker 1>people intentionally try to clog a network hit me up

0:29:44.320 --> 0:29:47.240
<v Speaker 1>with it. That would be a do OS denial of

0:29:47.280 --> 0:29:54.000
<v Speaker 1>a denial of service attack. UM. And basically, in these attacks, UH,

0:29:54.080 --> 0:29:59.320
<v Speaker 1>what happens is someone will intentionally send as many packets

0:29:59.360 --> 0:30:04.120
<v Speaker 1>as possible to the same spot. So basically, remember we

0:30:04.120 --> 0:30:08.240
<v Speaker 1>were talking just a few moments ago about how routers

0:30:08.280 --> 0:30:10.760
<v Speaker 1>are aware of what else is going on in the network,

0:30:11.000 --> 0:30:13.800
<v Speaker 1>and they talk to one another and they can they communicate. Well,

0:30:13.800 --> 0:30:16.840
<v Speaker 1>if you know where there is a specific router, uh.

0:30:16.880 --> 0:30:20.360
<v Speaker 1>And it leads to say, say you're some someone who

0:30:20.480 --> 0:30:22.440
<v Speaker 1>is who has a grievance against the company, and you

0:30:22.480 --> 0:30:26.320
<v Speaker 1>know where their their router is, you can send you know,

0:30:26.400 --> 0:30:29.280
<v Speaker 1>billions of packets to it. Uh. Someone's going to correct

0:30:29.320 --> 0:30:31.160
<v Speaker 1>me and say they can't be that many, but let's

0:30:31.160 --> 0:30:33.000
<v Speaker 1>say lots and lots of packets to it in an

0:30:33.040 --> 0:30:36.160
<v Speaker 1>attempt to overwhelm the router and give it so much

0:30:36.200 --> 0:30:39.200
<v Speaker 1>traffic that it cannot UM handle it, and it will

0:30:39.200 --> 0:30:43.280
<v Speaker 1>cause it to UH have errors. Basically, it will become

0:30:43.320 --> 0:30:48.000
<v Speaker 1>really sluggish or possibly even have it just shut down. Yeah,

0:30:48.280 --> 0:30:50.560
<v Speaker 1>it's certainly been known to happen in then variation of

0:30:50.600 --> 0:30:53.400
<v Speaker 1>this which is becoming more common as the d d

0:30:53.520 --> 0:30:56.280
<v Speaker 1>O S or distributed denial of service attack, which happens

0:30:56.280 --> 0:30:58.800
<v Speaker 1>a lot in a lot of cases with UH bot

0:30:58.840 --> 0:31:02.280
<v Speaker 1>nets where people have UM installed some kind of malware

0:31:02.280 --> 0:31:04.520
<v Speaker 1>on their computer and someone is running this attack to

0:31:05.360 --> 0:31:09.840
<v Speaker 1>UH you know, basically take over possibly thousands of computers

0:31:09.840 --> 0:31:12.520
<v Speaker 1>and have all of them send an attack against one

0:31:12.640 --> 0:31:15.600
<v Speaker 1>target at the same time. Which, as you might imagine,

0:31:16.280 --> 0:31:20.120
<v Speaker 1>if you had thousands of computers working on this problem

0:31:20.160 --> 0:31:22.880
<v Speaker 1>as it were sending sending requests at the speed of

0:31:23.000 --> 0:31:26.120
<v Speaker 1>light all to a single target, it's it's very easy

0:31:26.160 --> 0:31:29.479
<v Speaker 1>to overwhelm a single router with that kind of UH

0:31:29.720 --> 0:31:32.600
<v Speaker 1>with that kind of traffic. So UM when you when

0:31:32.640 --> 0:31:35.560
<v Speaker 1>you hear about these attacks, you can keep that in mind,

0:31:35.600 --> 0:31:38.560
<v Speaker 1>that that there's some router somewhere that it's doing its

0:31:38.880 --> 0:31:41.280
<v Speaker 1>level best to handle the traffic, but it is just

0:31:41.360 --> 0:31:45.600
<v Speaker 1>not keeping up with a flood of UH packets swarming

0:31:45.600 --> 0:31:49.720
<v Speaker 1>at it. And also on that same note, because a

0:31:50.040 --> 0:31:54.440
<v Speaker 1>router is essentially a computer. You can install software on

0:31:54.560 --> 0:31:58.840
<v Speaker 1>that router so that it has its own protections against

0:31:58.840 --> 0:32:02.920
<v Speaker 1>such things. So when you hear about people talking about firewalls,

0:32:03.160 --> 0:32:05.040
<v Speaker 1>there are various ways you can have a firewall. You

0:32:05.080 --> 0:32:06.800
<v Speaker 1>can a computer firewall, you can have it as a

0:32:06.800 --> 0:32:08.959
<v Speaker 1>software layer, you can have it as a hardware layer. Well,

0:32:09.040 --> 0:32:12.120
<v Speaker 1>routers kind of a hardware layer level firewall. A lot

0:32:12.160 --> 0:32:15.840
<v Speaker 1>of routers come with a firewall system in place that

0:32:15.920 --> 0:32:18.719
<v Speaker 1>you can configure once you set up your router, and

0:32:18.760 --> 0:32:22.160
<v Speaker 1>this will help protect your home network system from intrusions

0:32:22.760 --> 0:32:27.239
<v Speaker 1>from malware coming in, uh, from unrequested data coming in,

0:32:27.400 --> 0:32:30.440
<v Speaker 1>so sort sort of a spam protector as well. UM,

0:32:30.480 --> 0:32:33.880
<v Speaker 1>and routers can also have other kinds of software programmed

0:32:33.880 --> 0:32:38.560
<v Speaker 1>into them, things like encryption, UM, intrusion detection, that kind

0:32:38.560 --> 0:32:42.720
<v Speaker 1>of stuff. So, uh, depending on the model of router,

0:32:43.000 --> 0:32:46.600
<v Speaker 1>that'll that'll tell you what kind of protection is built

0:32:46.640 --> 0:32:50.240
<v Speaker 1>into the system. And uh, you know, it's not uncommon

0:32:50.280 --> 0:32:54.920
<v Speaker 1>to find routers come with firewall software and pre installed

0:32:54.960 --> 0:32:57.560
<v Speaker 1>in the router itself, which is also very useful. It

0:32:57.600 --> 0:33:00.000
<v Speaker 1>do highly recommend that if you know, if you're setting

0:33:00.080 --> 0:33:02.560
<v Speaker 1>up a home area network and you want to uh,

0:33:02.720 --> 0:33:04.760
<v Speaker 1>you want to have a router there to connect to

0:33:04.760 --> 0:33:08.320
<v Speaker 1>the internet. Setting up a firewall is a very good stuff.

0:33:08.400 --> 0:33:11.680
<v Speaker 1>It's not just like any other security system on the Internet.

0:33:11.720 --> 0:33:15.120
<v Speaker 1>I have to stress it's never full proof. You're never

0:33:15.160 --> 0:33:17.760
<v Speaker 1>going to have the perfect security system because people are

0:33:18.520 --> 0:33:23.840
<v Speaker 1>ingenious at getting around uh firewalls and other kind of barriers.

0:33:23.880 --> 0:33:28.200
<v Speaker 1>But it does mean that you're going to prevent the

0:33:28.320 --> 0:33:32.240
<v Speaker 1>overwhelming percentage of attacks from getting to you because most

0:33:32.280 --> 0:33:36.640
<v Speaker 1>people are also lazy, so they're gonna aim for a

0:33:36.680 --> 0:33:39.479
<v Speaker 1>wide array of targets and they're gonna be happy if

0:33:39.480 --> 0:33:41.640
<v Speaker 1>they just hit a few of those targets. They're not

0:33:41.680 --> 0:33:44.920
<v Speaker 1>necessarily aiming directly for you, unless you're some sort of

0:33:45.240 --> 0:33:49.160
<v Speaker 1>important individual with like a government or perhaps a news

0:33:49.200 --> 0:33:52.120
<v Speaker 1>agency or something like that. If you have like a

0:33:52.200 --> 0:33:55.440
<v Speaker 1>high profile status, then you might have to worry about

0:33:55.520 --> 0:33:59.160
<v Speaker 1>more stringent security. But for the average user, it doesn't.

0:33:59.200 --> 0:34:05.000
<v Speaker 1>You know, a decent viral wall is enough. Yeah, Indecent

0:34:05.000 --> 0:34:09.440
<v Speaker 1>fire walls are never enough. Well. I think that's a

0:34:09.480 --> 0:34:12.279
<v Speaker 1>good discussion on routers. We really pretty much covered the

0:34:12.280 --> 0:34:13.840
<v Speaker 1>basics there, and like I said, if you want to

0:34:13.920 --> 0:34:16.480
<v Speaker 1>learn more, visit how stuff works dot com. Check out

0:34:16.480 --> 0:34:19.520
<v Speaker 1>our articles on how routers work and how network address

0:34:19.560 --> 0:34:23.239
<v Speaker 1>translation works. Um those those articles are very helpful to

0:34:23.320 --> 0:34:26.600
<v Speaker 1>understand the ins and outs of how this data goes across.

0:34:26.600 --> 0:34:28.800
<v Speaker 1>There's also some great animations and everything that show this

0:34:28.880 --> 0:34:31.680
<v Speaker 1>in action. So if you have problems visualizing it, check

0:34:31.680 --> 0:34:34.759
<v Speaker 1>out the website. It really does help. And guys, if

0:34:34.800 --> 0:34:38.200
<v Speaker 1>you have any requests that you would like us to

0:34:38.320 --> 0:34:42.600
<v Speaker 1>address uh huh, you can let us know via email

0:34:42.640 --> 0:34:46.400
<v Speaker 1>our addresses, text stuff at how stuff Works dot com,

0:34:46.520 --> 0:34:49.200
<v Speaker 1>or send us a little message on that Facebook or

0:34:49.320 --> 0:34:52.960
<v Speaker 1>Twitter thing. Both of those places are handle is tech

0:34:53.040 --> 0:34:55.840
<v Speaker 1>Stuff hs W and Chris and I will talk to

0:34:55.880 --> 0:35:01.080
<v Speaker 1>you again really soon. Be sure to check out our

0:35:01.120 --> 0:35:04.480
<v Speaker 1>new video podcast, Stuff from the Future. Join How Stuff

0:35:04.520 --> 0:35:07.440
<v Speaker 1>Work staff as we explore the most promising and perplexing

0:35:07.520 --> 0:35:12.200
<v Speaker 1>possibilities of tomorrow. The How Stuff Works iPhone app has arrived.

0:35:12.320 --> 0:35:19.440
<v Speaker 1>Download it today on iTunes, brought to you by the

0:35:19.480 --> 0:35:22.759
<v Speaker 1>reinvented two thousand twelve camera. It's ready, are you