Thanks for breaking it down this way. Most instructors start by listing the layers and then say what they do and by that time I see now why I was often confused and mixing things up. You teaching it this way simplifies things going forward. I finally feel like some of the holes in my understanding are being filled. I shouldn't have near as much confusion on what layer is responsible for what. and it won't matter if we're talking OSI or TCP/IP suite. Thanks a bunch!
As for a non-technical person this helps me so much. Have been trying to understand the logic behind this series for ages! Hope you continue making this kind of videos. 👍🏻👍🏻👍🏻👍🏻
Its not the the topic but the simplicity of explanation that makes it a great video series. I am a control system engineer (13 Years) who was looking for a logical connection to networking basics. If i can get the basics in my head, working with relevant embedded boards would become easy. The detail of a topic can only be remembered if the topic's place in larger scheme is understood well. so thank you again.
So through what I understand I think I have come up w/ a simplistic way of breaking down the video and if anything I say is wrong please let me know so I can adjust accordingly. I'm going to breakdown this entire video using & explaining all 5 layers of a network through the simple action of signing into Netflix from any device. Step 1: You go to Netflix itself which is the Application Layer Step 2: You type in your Username & Password to go through the Transport layer, which through TCP will check & confirm that 1.Your Account Exists within Netflix's system and 2.Confimrs the Username & Password you typed in is spelt correctly. Otherwise, TCP will then redirect to a new page with the message "this account doesn't exist" or "The Username/Password you typed is incorrect Step 3 The Network Layer, Netflix checks Your IP Address to confirm you've logged into whatever internet provider you're trying to sign in on before and making sure it's not your friend or neighbor in another home trying to log into it Step 4: The Data-Link Layer, Netflix Checks your MAC address to confirm you've logged into Netflix through your current device before and if it's a new one may send a confirmation message like "new device? Is this You?" and finally Step 5: The Physical layer has successfully signed you into Netflix and allows you to stream your show
At 6:23, you said the IP address identifies the network where the computer is, but its the Subnet Mask that identifies the network and not the IP address. The IP address is only identifying the computer that is making the request to the server.
Hi Danny, the IP address and the subnet mask are needed to complete that thought. If you don't have the subnet mask you won't know what the network is from just the IP address, and the IP address will need the subnet mask to identify which part of its address is the network and which part is the host. ie. If you have a subnet mask of 255.255.248.0 and no IP address, it's useless. You cannot tell which network a host lives in. If you have and IP address without a subnet mask, the computers won't know how to reach the network. Similar to how Keith described it, this would be a house without a street identifier. Hope that helps! Thank you for learning with us.
Hi Aboubaker, whenever a new device is plugged in and discovered by a switch it grabs the MAC address and puts it in a table. Then when traffic is forwarded into or out of the client it has the MAC address already. Hope that helps!
@@ZEROToWolf , yes, the OSI Model is a bit different from the TCP/IP Stack which is apparently presented here; however, they are somewhat related. So, the TCP/IP stack contains 4 layers that is well known by the acronym ATIN (Application [mapped to the Application, Presentation and Session layers of OSI), Transportation Layer (which maps to the Transportation Layer of OSI), Internet (which maps to the Network Layer of OSI) and Network Access (which maps to both the Data Link and Physical Layers of OSI). One thing that confuses me with this video, though, is that the last two layers of OSI (Physical & Data Link) is actually mapped to the Network Access layer of the TCP/IP stack. I don't understand why he have them listed here as separate. Personally, to me, the presenter seems to be presenting a hybrid model which have some aspects of TCP/IP and OSI; which is rather confusing.
This guy made several months of learning easy and quick in just a couple of clips! I love this guy!
Thanks for breaking it down this way. Most instructors start by listing the layers and then say what they do and by that time I see now why I was often confused and mixing things up. You teaching it this way simplifies things going forward. I finally feel like some of the holes in my understanding are being filled. I shouldn't have near as much confusion on what layer is responsible for what. and it won't matter if we're talking OSI or TCP/IP suite. Thanks a bunch!
Thank you for that feedback Majestic! Much appreciated.
@@KeithBarker Thanks for the free education!
As for a non-technical person this helps me so much. Have been trying to understand the logic behind this series for ages! Hope you continue making this kind of videos. 👍🏻👍🏻👍🏻👍🏻
Thank you so much, I am in InfoSec and greatly appreciate these videos!! 🤘
Love the way you explain technical stuff,Much appreciate it Keith,U r an inspiration... . Keep it up,Love from India
Its not the the topic but the simplicity of explanation that makes it a great video series. I am a control system engineer (13 Years) who was looking for a logical connection to networking basics. If i can get the basics in my head, working with relevant embedded boards would become easy. The detail of a topic can only be remembered if the topic's place in larger scheme is understood well. so thank you again.
I really like the way you teach ...I hated n/w earlier but now I am understanding concepts . Thanks thanks thanks thanks a lot
Excellent simple way of teaching. Thank you.
Yes understand how network is working in side the computer.
Sir I like your teaching style.👌👌👌
You explained it real good. Even a layman can understand it. thanks a lot.
this guy is a good teacher
Amazing videos! Thanks a bunch for sharing them with us, Keith!
Love the way you explain it. It's easier to understand. Thank you!
Glad it was helpful!
Thank you so much for the help...really appreciate and so grateful for the help....
May god bless you 🙏
This really helps me in my class. Thank you!
Glad to hear that!
@@cbtnuggets yep I may be going up the wall with the virus but im still a kind-hearted girl
Congratulations! You are amazing!
such a nice and sweet guy. tnx man.
Thanks Keith,
Really very much helpful
So through what I understand I think I have come up w/ a simplistic way of breaking down the video and if anything I say is wrong please let me know so I can adjust accordingly.
I'm going to breakdown this entire video using & explaining all 5 layers of a network through the simple action of signing into Netflix from any device.
Step 1: You go to Netflix itself which is the Application Layer
Step 2: You type in your Username & Password to go through the Transport layer, which through TCP will check & confirm that 1.Your Account Exists within Netflix's system and 2.Confimrs the Username & Password you typed in is spelt correctly. Otherwise, TCP will then redirect to a new page with the message "this account doesn't exist" or "The Username/Password you typed is incorrect
Step 3 The Network Layer, Netflix checks Your IP Address to confirm you've logged into whatever internet provider you're trying to sign in on before and making sure it's not your friend or neighbor in another home trying to log into it
Step 4: The Data-Link Layer, Netflix Checks your MAC address to confirm you've logged into Netflix through your current device before and if it's a new one may send a confirmation message like "new device? Is this You?"
and finally
Step 5: The Physical layer has successfully signed you into Netflix and allows you to stream your show
very great ! explanation
At 6:23, you said the IP address identifies the network where the computer is, but its the Subnet Mask that identifies the network and not the IP address. The IP address is only identifying the computer that is making the request to the server.
Hi Danny, the IP address and the subnet mask are needed to complete that thought. If you don't have the subnet mask you won't know what the network is from just the IP address, and the IP address will need the subnet mask to identify which part of its address is the network and which part is the host.
ie. If you have a subnet mask of 255.255.248.0 and no IP address, it's useless. You cannot tell which network a host lives in. If you have and IP address without a subnet mask, the computers won't know how to reach the network. Similar to how Keith described it, this would be a house without a street identifier. Hope that helps!
Thank you for learning with us.
Thank you So much
thanks alot. at 7:00 you said that the client send the mac add of server i am asking how tha client know that mac add
Hi Aboubaker, whenever a new device is plugged in and discovered by a switch it grabs the MAC address and puts it in a table. Then when traffic is forwarded into or out of the client it has the MAC address already. Hope that helps!
Very good channel I love't
Just wanted to ask aren't there suppose to be 7 layers
thats the OSI model.
@@linasaid8925 im confuse so it's different from the osi model
@@ZEROToWolf , yes, the OSI Model is a bit different from the TCP/IP Stack which is apparently presented here; however, they are somewhat related. So, the TCP/IP stack contains 4 layers that is well known by the acronym ATIN (Application [mapped to the Application, Presentation and Session layers of OSI), Transportation Layer (which maps to the Transportation Layer of OSI), Internet (which maps to the Network Layer of OSI) and Network Access (which maps to both the Data Link and Physical Layers of OSI). One thing that confuses me with this video, though, is that the last two layers of OSI (Physical & Data Link) is actually mapped to the Network Access layer of the TCP/IP stack. I don't understand why he have them listed here as separate. Personally, to me, the presenter seems to be presenting a hybrid model which have some aspects of TCP/IP and OSI; which is rather confusing.
Yeah!! 7 layers there are!
Shame this video didn't stick with the common mnemonic - "A TIN" for Application layer, Transport layer, Internet layer and Network Access layer.
Hello