1.

1 Networking Basics
Wednesday, May 27, 2020 6:38 PM

1. What is Subnetting Page 1

1. What is Subnetting Page 2
1.2 Networking Traffic
Thursday, May 28, 2020 6:04 AM

1. What is Subnetting Page 3

1. What is Subnetting Page 4
1. What is Subnetting Page 5
1. What is Subnetting Page 6
Transcript
Thursday, May 28, 2020 6:24 AM

Hi and welcome. My name's Michael. And in this lesson, we're going to be looking at network traffic. Now that we're familiar with the basic components that make up
a network—that is, NICs, switches, and routers, we can talk about how the data moves through the network. Let's get started. So I'm here on the second section on
the left network traffic within the interactive diagram, and the first portion of this section is going to be network traffic methods. And so here we have our small
network that we looked at in the last lesson, and we're gonna talk about the three ways traffic can move through the network. The first method, the most common, is
unicast. Unicast is one to one—that is, one device on the network sending traffic to one other device on the network. Now, for the purposes of network topology,
switches don't really count. They just forward the packets on; they're not a destination. So in this example, the green computer here on the left is sending data
through the switch to the orange computer here at the bottom. That's unicast. One-to-one. Again, that's the most common method of traffic. Another method is multi
cast. This is one to several or one too many. So in this example, the green computer is sending data at the same time to these three computers, the three orange
computers at the bottom. And the reason you might do this would be a You have a server form and they're keeping each other up to date, and they're doing so
through multicasting. Now, if we follow this kind of as a thought experiment, we'll see there's going to be a lot of cross talk. If every computer is multicasting to every
other one, then it's going to exponentially grow, and we're going to saturate our network, and that could become a problem. But there are valid use cases for multi
cast. The last form of traffic is broadcast, and this is one to all. So this is our green pewter here on the left is sending out traffic to every computer on the land or every
device on the land, every destination. And because our router is part of our LAN, it is also receiving that data. Now, why would a computer do this? We'll talk about
that when we look at addressing and get into ARP. So let's talk about the OS I layers. I don't want to spend a ton of time on my layers there, an important abstraction
model, and it's important to understand them. But in the context of sub netting, you just really have to have some exposure to him. You don't you don't need to have
a a complete and thorough understanding of the O. S. I layers. Just know that the OS I layers or an abstraction model that all network traffic follows or passes through,
and so traffic would begin at the application layer, and I've kind of condensed five through seven, since this is all managed by the application, so it starts at the
application layer. It moves down through the transport layer down through the network, layer down through the data link layer across the physical layer. And then it
comes back up through the physical, through the data through the network, through the transport and into the application on the other side. So let's look at the
application layer, and I've condensed layers five through seven again. The application presentation in session layers. These air typically managed by the application
itself, and they provide the interface for the user to communicate. The data being passed at the application layer is user data, and so a real life example of this would
be a Web browser. It is the application that you are using to interface with, and the data is kind of being managed by the application. So if you're watching this video
on the Internet, your Web browser is managing that it is managing at the application. The presentation of session later aim or conceptual example In probably one of
the best ways I've ever seen this explained, was ordering a pizza for dinner. The application layer is the phone that you used to place the order. It is the user interface
that you're using to place the order. The presentation layer is the fact that you both need to be speaking the same language. So you're speaking English and you call
and the pizza store answers. They're speaking English. You're both able to have that conversation. That's kind of the abstraction of presentational layer. And then for
the session layer. The person that you're calling the pizza store has toe answer. There has to be someone on the other end that says hello. So moving down into the
transport layer, the transport layer defines how data will be sent. It provides validation and security in the data being passed that this layer is segments that includes
the user data chunked into segments. This is the layer where fire walling occurs. If you're familiar with firewall, a conceptual example again. So you've called the store.
You've ordered the pizza. This is where que es gets involved. And they make sure they only the pizza that you have ordered only the toppings that you want Go on
that pizza and that you don't get the wrong pizza. Next we have the network layer. This is layer three, and this handles routing the packets across the network through
the best route to reach the destination. Based on your I p address again, we're going to talk about addressing coming up. Just know that I p address ng a P addresses
our sources and destinations on the network layer. In our conceptual example, the pizza store is going to use GPS to find the best route to your house. Next we have
the data link layer. This is layer two. The data link layer handles communication between adjacent network notes via the physical addressing. Mac addresses. Again,
we'll get into that when we talk about addressing, Just know that I p addresses for Layer three Mac addresses for layer to for our conceptual example. The pizza store
needs your full address. It needs to know right down to the house number where that pizza's going. And then, lastly, we have the physical layer. This is the physical bit
level transmission layer. So this is the wire from your NIC to your destination. It could be radio waves. It could be fiber with pulses of light. But this is the physical
connective ity. In our conceptual example. You've ordered the pizza. They've made the right pizza. They've got the address to your house. They've got the full address
to where to take it. This is the roads they're going travelling to get that pizza delivered. So that's the OS I model. And if you do any work with networking, you're going
to become relatively familiar with layer to layer three, and layer for layer four is going to be the port to port Transmission. Layer three is going to be I P address toppy
address transmission and layer two is going to be Mac address to Mac address transmission. So let's look at the actual data. So here we have a T c p I P. Example. We
have our application layer. Here. We have our transport layer here. Network layer here, datalink layer here. So, looking at the application layer, your application is
going to create some data. Cem user data by virtue of you interacting with it and it making network calls, it's going to assemble. Maybe Webb requests. It could be a
form. Your posting, something like that. It will have its own data set that it is transmitting across the wire. This is the whole point of having the network. Is this data
here? The user data moving back and forth a lot of times, the application itself will put an application header in front of that data. Some of that. The application on the
receiving side has some context with what to do with it. So the application is going to create some user data, and then the applications could put a little header in
front of it. Now, as that data moves down into the transport layer layer four in the T c p. I P. Example. Now we could be using UDP, but that's it's kind of a nun verified
stream of data. There are other protocols as well, but TCP is the most common and a good fit for our example here, the TCP header is going to be placed in front of
this one of the things this is going to be referred to as a segment. So what? The transport layer. You have segments that the network layer, you have packets. And if
the datalink layer you have frames in the Ethernet example So the transport layer is going to have a TCP header, and the data in this header is going to be the source
port and the destination port. So if you're making a request over the web, you're sore sport. Maybe something high and un privileged. So, you know, port 65,000
something. But your destination port is probably gonna be port 80 or 4 43 at your destination. That would be http waged B s. It's a regular website or or it s a cell site.
Some additional data is going to be sent like the sequence number. The acknowledgment number data offset reserved control flags. Window says checks on an urgent
pointer. The checksum is notable because this is the mathematical hash that will be used to make sure that the segment integrity has not been compromised. If it has,
it can request a re transmission moving down into the network layer. We're going to have an I P header perceiving the packet. So the packet is going to contain
segment data application data user data. So the I P Header is going to be looking at the source I P address and Destination I P address and you can see there's a lot of
other information contained in the IP header. And a lot of this is to facilitate smooth transmission. Again, we have a checksum to verify integrity. We have a time to
live. So how long it can exist on the network? The protocol. Which version of I P are we using some basic environmental data version in length and then we have
options and padding to make sure the math all works something in terms of how many bets Everything is moving down into the datalink layer. We now have a
Ethernet frame. And so the frame data is going to include packet I, P data segment, application data and, of course, the user data. One thing to keep in mind is that
each one of these frame packet segment so forth have different maximum and minimum sizes. So think of them in relation to one another. The lower layer dictates
the maximum size of the data that can be handled from the layer above. One difference of the frame is that the frame is going to have a header and a footer. So I
think it was a frame around a painting. It completely encapsulate ce the frame data. So looking at the frame header, we're going destination address, Mac address and
source address. Mac address. TCP Header was port to port. IP header is IP address to IP address. The frame header is Mac address to Mac address. So looking back at
that with the preamble which will synchronize where the frame starts, we have our destination address, a source address, the lengthen type, all of that packet data
and then the frame check sequence, which is a lot like to check some for the other two headers, and he is used to detect compromised or corrupt frames. So the term
packet is a little loaded. Let me let me talk about the semantics of that real quick. The even at protocol on the physical layer. Layer one, the unit of data, is often called
an Ethernet packet, which has an Ethernet frame that's layer to here as its payload. But the unit of data of the network Layer three, is also referred to as a packet. So
you hear the word packet used in a couple of different contexts. Another semantical difference between the packing, the frames, the frame envelopes, the payload
with a header in a trailer. Like I said, So now we know the basic components of networking, and we have a pretty good understanding of how that data moves through
the network in a good position to actually talk about sub netting, why we do it, how we can start doing it and things of that nature. This lesson is now complete.
Thanks for watching

1. What is Subnetting Page 7

1.3 Networking Segmentation
Thursday, May 28, 2020 6:25 AM

Big open network

Isolation

1. What is Subnetting Page 8

Scalling

1. What is Subnetting Page 9

1. What is Subnetting Page 10
1.4 Addressing
Thursday, May 28, 2020 6:42 AM

1. What is Subnetting Page 11

1. What is Subnetting Page 12
1. What is Subnetting Page 13
Transcript
Tuesday, June 2, 2020 6:20 AM

Hi and welcome. My name's Michael and in this lesson, we're going to talk about network addressing. So think about this for a second. If someone wants to send
you a letter in the mail or even an email, they need to know your address. They need to know where to send it. Likewise, for something to be reachable on the
network, it must be addressable. Let's get started. So I'm here in the interactive diagram and I'm on the fourth section here on the left. Add dressing and what we
have here is an example of an I P V four address 192.168 That 1.101 now Ah, pv four is version four of the IP Protocol, if you will. It is Internet Protocol version
four, IPv4, and it's been around since about the early eighties. Now, one of the limitations of a PV four is that there is an upper limit of about four point
3,000,000,000 addresses in total. So let's look at the anatomy here We have four numbers separated by period. Each one of these groups is called an octet. So an
IPv4 address is comprised of 4 8-bit sections called octet. It's the first octet is one, then to the second. It's 168 The third is one, and the fourth is one of one. Each
octet has a lower limit of zero in an upper limit of 255 for a grand total of 256 values. And since each octet is an eight bit section, eight times four is 32 for a
grand total of 32 bits and total length. So why do we call these octet? It's well, if we look at one we see it is an eight bit binary number. So eight oct octet the
minimum value of an eight bit binary number is zero. The maximum value of eight bit binary number and that's all ones is going to be 255. So that is the basic
anatomy of an IPv4 address. Let's look at an IPv6 address. This is the sixth version, or version six, of the IP protocol. This has been around since about 1998 and it
supports 340 trillion addresses. I will say the adoption of IPv6 has slowed somewhat. It was delayed due to network address, translation or napping, and that
permits mapping a private i p toe a public I p. And really, what we're seeing is a lot of the carrier networks like AT and T, Verizon, etc., are moving to IPv6, but
enterprises are a little slower and somewhat behind, but the pressure is off due to NATing. And if we look at the address, it is a little longer than a regular IPv4
address, you're not going to be able to memorize something like this very easy. The one thing that we can do to make it look a little less long is everywhere there
is a leading zero. So, just like on our original example, one down 2.168 dot 1.1 a one. We could read this as 192.168 dot 001 dot wanna one, and it's the same
without TV. Six. We can actually compress these leading zeros, and if you have sections of leading zeros, those can all be compressed down and denoted by
double colon. So still not easy to remember, but a little less too right. Moving back to the address itself, we can see that it is comprised of eight sections. Each
section is a 16 bit field. Each digit is a hex, a decimal, a hex. A decimal is a base 16 number that is zero through nine. Just like our decimal base. You know, the
0123456789 and then 10 11 12 13 14 15 someone and so forth. However, it goes from zero to F. And so if we look down here, we can see you know, the zero
starts at zero, and then when we get to nine, we're still at nine. But for the number 10 it is represented by an A. 11 is B 12. C 13 is D 14. E 15 is F for a total of 16
values. And so if we look at this as a hole in each hexi decimal number is a four bit number. We have a 128 bit address. Now I p v six addresses are are somewhat
unique. The first half is considered the network portion the second half is considered the host portion and is often derived from the Mac address. What this
means is that the first half of the address is the network address. This denotes what network this address belongs to. The back half denotes the host number or
the host address within the network. That is the front half. This is important to understand because sub netting IPv4 happens in the same manner.

So if this host portion for an IPv6 is derived from the Mac address, what is the Mac address? The Mac address is a 48 bit number. It's also a hexi decimal, and it is
the fingerprint of the network interface card. So if we look at the anatomy we see it's a 48 bit number in the first half is considered the O. U I or organizationally
unique identify. This number denotes the manufacturer. So if this was a Cisco card, all Cisco cards would start with, you know, b2:00: e5. Now that doesn't mean
that the Mac address could be changed, but that would be the difference between a universal or a local Mac address. A universal Mac addresses one assigned by
the manufacturer. A local Mac addresses one that it's created programmatically or or manually. So if you're using a VM or something like that, it's going to create
local Mac addresses. So the IPv4 and IPv6 addresses are the addresses on the network. The Mac address is the hardware address at the Network Interface Court.
It is the hardware fingerprint, if you will. So we have to have some way to map an I P address to a Mac address. And the way that we do this is through AARP.
AARP stands for address resolution protocol. So here we are, back on our sample Small network. The 1 91 681.0 slash 24. This is our land. If you remember in our
computer down here has a an I. P. Address of 192.168 dot 1.212 If it wants to communicate to i p address 192.168 dot 1.101 It needs to know the physical
address the Mac address to communicate to now. It wouldn't need to know that if the destination was outside of the local network, then it would use the Mac
address to get to the router. And so how does it get that address? It sends a broadcast request. And if you remember, a broadcast request goes to everything on
the LAN. So it's going to send this broadcast request, and it's going to say, Hey, who has 192.168.1.101? Tell me, 192.168.1.212. Now the host with that target
address, 192.168.1.212, is going to respond. It's going to say, Hey, I have that IP, 192.168.1.101, and it's going to send this response back unicast. And if you
remember unicast, that is 1 to 1. So the request goes out broadcast. The response comes back unicast for ARP. At this point, both of these devices are aware of
one another's Mac addresses, and that information is stored in what's called the AARP table. In the next lesson, we're going to start talking about what this I P
address and other examples look like in binary so that we have some understanding as to how network masks are applied. And we need to know that so that we
can see how we apply network masks when creating sub nets. This lesson is now complete. Thanks for watching.

1. What is Subnetting Page 14

1.5 Binary
Tuesday, June 2, 2020 6:37 AM

1. What is Subnetting Page 15