Dude, what a great explanation of the encapsulation process. I was reading Odom Wendell's Cisco CCNA book. He doesn't quite explain it in a way that worked for me. This video broke down this process that made sense. Thank You!
I understand why the packets are built but not the how they are built. It would be very useful to also know, *where* does the transport layer get the port numbers from? Where does the Network layer get the IP addresses and how does the data layer get the MAC address of a machine that is on the other side or the world?
Hi, this is a good tutorial. I am just a bit confused about a few things. I thought MAC addresses were only there to resolve local IP addresses? So if a packet is moving from one router to another and they are in different networks, how will it get the Mac address?
I have a question, there are 2 computers connected directly and configured to be a point to point network I mean PC A and PC B. And I want to send a data (word, name, characters) from one computer to another (from A to B), How the computer B knows that the package have been send completely from computer A, in what layer this happen?
I think session transportation and perhaps network layers unpacking and tagging headers putting hop to hop end to end layers and making the necessary routing process but I’m not sure someone please elaborate for us both
How is a URL translated into an IP, since the DNS is not on my (source) PC? If my PC does'nt know the destination IP, does it mean it first encapsulates any segment with the IP of the ISP DNS? Thanks
I know this is an older question but to answer for the future. When this happens, your PC first reaches out to the DNS server to get the IP back before starting the connection to the host. You can download Wireshark to see this process for yourself. You'll notice that if you go to a site that you haven't been to before, there is first a DNS request sent to get the IPs and then the TCP request is sent after you get the IPs back.
I understand everything except what unpacks the segment layer and how. The router needs to remove the frame layer in order to see the ip address, and then repackage the data block in another frame and then send it off, but what I don't understand is where the segment is looked at. The destination port is 80, and I thought that that was handled at the router level as well (firewalls are usually on the router), but you didn't really talk about that part. What am I missing?
Probably one of the best questions I’ve received in a while... First of all, routers are routers. Not firewalls. Yes you can implement features that permit or deny the flow of traffic, but it should be a routers prime job of only routing. Firewalls, are ‘beefed’ up routers with plenty of more features allowing the control of traffic. Segments for source and destination port information are providing a service to the layers above it, so the application layer. TCP has addresses called ports, and the application is assigned to one of the addresses, port 6000 for example. TCP will segment these data and put TCP headers on the data segment. The TCP headers include the source and destination port number. This then gets added to the packet where now we need to know where the information is being sent to, and from for network communication. Then the frame. Each of these get encapsulated and decapsulated by software built into the nic’s on your end user devices or networking equipment. Each device will know what information it needs and decapsulate the packet until it learns that information. Firewalls control our traffic, same with access control lists on routers. This can allow certain traffic to and from different applications. Maybe one application has the ability to use http, https, telnet, and ssh. But http and telnet are not secure so we can block traffic to/from that one application for those two based on the port information, but we still need to access it... so we will allow the secure https or ssh traffic. Again, supporting the application. Hope this helped clear some of that up.
Dude, what a great explanation of the encapsulation process. I was reading Odom Wendell's Cisco CCNA book. He doesn't quite explain it in a way that worked for me. This video broke down this process that made sense. Thank You!
wireshark never made this much sense , thanks man. The way you break down the concepts , excellent !
The best video i've found on UA-cam about TCP/IP model. I saw many in german and polish, but just yours is coplete! TNANK YOU SO MUCH!
These trainings are amazing. I understand all of this so much better now.
Thank You so much, your channel and your explanation is really amazing!
Please keep your channel updated!
The pacing is intense! Loved it though. It gave me a fuller understanding on the segment, packet, frames and bits part of the OSI model. Thank you!
excellent video, clears many of the obvious doubts that one can have while studying for ccna certification
This is the best explanation I've got on Networking, thank you so much sir.
I am finally understanding the difference! Thanks!
Had to slow it down to understand- I got it NOW !!!! Thanks !!!
Great quality video, hope to get some notifications from any new work in the future
Excellent clear and concise explanations I now understand the encapsulation process thank you :)
The best video on youtue explaining this, trust me have done lots of searching..thankyou, keep doing more videos, pls cover SAN also..
Than you so much!! Awesome instructor. This is amazing content
Well explained sir!
A very helpful video. Thanks
Well explained.
I understand why the packets are built but not the how they are built. It would be very useful to also know, *where* does the transport layer get the port numbers from? Where does the Network layer get the IP addresses and how does the data layer get the MAC address of a machine that is on the other side or the world?
Very helpful！
Hi, this is a good tutorial. I am just a bit confused about a few things. I thought MAC addresses were only there to resolve local IP addresses? So if a packet is moving from one router to another and they are in different networks, how will it get the Mac address?
Very helpful
I have a question, there are 2 computers connected directly and configured to be a point to point network I mean PC A and PC B. And I want to send a data (word, name, characters) from one computer to another (from A to B), How the computer B knows that the package have been send completely from computer A, in what layer this happen?
I think session transportation and perhaps network layers unpacking and tagging headers putting hop to hop end to end layers and making the necessary routing process but I’m not sure someone please elaborate for us both
How is a URL translated into an IP, since the DNS is not on my (source) PC?
If my PC does'nt know the destination IP, does it mean it first encapsulates any segment with the IP of the ISP DNS? Thanks
I know this is an older question but to answer for the future. When this happens, your PC first reaches out to the DNS server to get the IP back before starting the connection to the host.
You can download Wireshark to see this process for yourself. You'll notice that if you go to a site that you haven't been to before, there is first a DNS request sent to get the IPs and then the TCP request is sent after you get the IPs back.
bloody brilliant
I understand everything except what unpacks the segment layer and how. The router needs to remove the frame layer in order to see the ip address, and then repackage the data block in another frame and then send it off, but what I don't understand is where the segment is looked at. The destination port is 80, and I thought that that was handled at the router level as well (firewalls are usually on the router), but you didn't really talk about that part. What am I missing?
Probably one of the best questions I’ve received in a while...
First of all, routers are routers. Not firewalls. Yes you can implement features that permit or deny the flow of traffic, but it should be a routers prime job of only routing. Firewalls, are ‘beefed’ up routers with plenty of more features allowing the control of traffic.
Segments for source and destination port information are providing a service to the layers above it, so the application layer.
TCP has addresses called ports, and the application is assigned to one of the addresses, port 6000 for example. TCP will segment these data and put TCP headers on the data segment. The TCP headers include the source and destination port number.
This then gets added to the packet where now we need to know where the information is being sent to, and from for network communication.
Then the frame.
Each of these get encapsulated and decapsulated by software built into the nic’s on your end user devices or networking equipment. Each device will know what information it needs and decapsulate the packet until it learns that information.
Firewalls control our traffic, same with access control lists on routers. This can allow certain traffic to and from different applications. Maybe one application has the ability to use http, https, telnet, and ssh. But http and telnet are not secure so we can block traffic to/from that one application for those two based on the port information, but we still need to access it... so we will allow the secure https or ssh traffic. Again, supporting the application.
Hope this helped clear some of that up.
what is data packet produced
Man, you talk fast but great video! Very well explained.
Very useful video...but at warp speed! :-)
Nice
You talk a little too fast, but it's a very good video.
Too fast sir. Couldn't tag along the speed.
😴😴😴😴
Excellent but you are too fast in explaining. It you explain this slowly it will be more excellent.
not helpful, you went a bit way too fast.
Talk too fast. Hard to follow.
sir this is not a race. you speak like u have to run somewhere not as a tutorial.