Hey guys in minute 16:00 I forgot to mention this is a WIFI configuration not wired . so all devices within range will receive the those packets since they are in radio vicinity and drop them if they are not intended for them. if that was wired than the router (acting like a switch) will be smart enough to only forward to required device by identifying which port it is connected to.
I was really confused until i saw this comment. Thanks! However, I do have a question, in a network of only wired computers, how could someone listen for packets? If the router is only sending the packets to the intended recipients, then I don’t see how someone could sniff packets unless they had access to that router. Basically, would tcpdump or wireshark work in a completely wired network?
in case of wifi, doesn't the client set the destination as a router(which is a default gateway for it) at some layer and then the router directs the packages to the server? So, basically, the server receives the package twice: first time from the client and second time from the router; but first package it drops at some lower layer as it doesn't know yet that it is the destination of that packag. Or in case of wifi, the router even doesn't takes a place in client-server communication? Why I'm asking, becasue at the moment when client sets the destination at data link layer it doesn't know what media will be used to transfer the data(wifi or wired connection) so it sets as a address its gateway
I feel like I want to quit my job and spend a few weeks just studying your backend topic videos. Really interesting stuff. I was even able to explain to my wife why she can't access homebanking in a starbucks.
I quitted my job and and I discovered this channel... I know that feeling, i think I need at least one month to watch all the videos and after that maaybe get another job 😆
Guys here are some jump codes to help you navigate, 2:15 public vs private ip address, 4:00 Application Layer, 5:30 Presentation Layer, 6:20 Session Layer, 7:20 Transport Layer, 9:20 Network Layer, 11:20 Data Link, 13:00 ARP protocol, 14:00 Physical Layer, 19:00 Why you shouldn’t connect to public WIFI I enjoyed making this video!
"Intended for you as a device, but not as an application" - Perfect way to explain the way the router works when you make a request to external network 👌
Hi Hussein, thank you for making this video. I just want to clarify one thing. At 16:20, you say that the stream of bits that are being sent from the client will go into server 1,2,3,4..etc essentially to all servers. This is not correct. I'm a software engineer working in networking domain, and in networking the direction of packets is either "unicast" (meaning it's directed to one client only), multicast (meaning it's directed to two or more known clients), or broadcast (meaning the traffic is directed to any machine that's on that network). In your case, since the server is hosted on machine C, the data is directed to that machine and it will only go to the router first and then to that machine regardless of the medium used to transfer the packet (Ethernet or WiFi). If the stream of bytes were transferred using WiFi, you are right in that the data will be broadcasted all over the place using radio waves but only the router will be able to interpret those packets, because that's how WiFi works, and the other machines (even if they have a WiFi receiver) will not be able to decode the packet and see the bit streams. Just wanted to point this out to clear any confusion. Thanks for making these video. They're very useful and informative.
@@devarsdk the physical layers knows that this is for him, and he then checks to what local ip he needs to redirects it request and then it broadcast the wave again and that;s for C
Summary of: OSI (Open Systems Interconnect) model, from a software Engineer's view (Please correct me if I'm wrong): Layer 1 Physical This is the physical layer, in which 1 and 0 data bytes can be sent as electric signals, wifi, or light via "the wire" Layer 2 Data Link These are the separation of the data bytes into frames. Notably, the frames will identify the source and destination MAC addresses of the devices' network card. Since electrical signals travel in all directions in a network, the data frames reach all devices in the network. Once the data frame is able to identify that the device is not the intended destination, the frames drop. In an unsecured network, this is where a malicious application can choose to not drop the frames, and steal the data. Layer 3 Network Once layer 2 is done, it generalizes the frames from MAC addresses to IP addresses. Layer 4 Transport This tranport layer further generalizes the network layer IP address into source and destination ports. Layer 5 Session Since there may be several TCP connections to one server at a time, with identical packet information from layers 1 through 4, we need a way to distinguish the session by ID to tag it. Layer 6 Presentation This is where the resource might be secured/encrypted with HTTPS/TLS by scrambling the HTTP request string. I didn't know HTTPS encrypted anything. I thought it was only a way to identify the true identity of a website. Also, encryption might be accomplished via VPN. At this step, if the data is encrypted, the model decrypts the information to reach step 7. It might be possible that a malicious attack to steal data can be avoided by encrypting. "This is where you can get screwed if you are on public wifi...people can sniff your data." Layer 7 Application This is where a client device makes a request to a server device, such as a GET request. This request contains a whole bunch of information, such as headers, cookies, content-type headers, etc, which is summarized into a string, so the string can participate with the rest of the OSI models as byte data.
Andres! Amazing summary thanks for taking the time to compile this. It would be nice to separate the summary based on the sender vs the receiver . Thanks for being a fan of this channel :)
It is a dry topic, but somehow even with your thick accent and minimalist presentation style, your charisma makes this video a joy to watch. Seriously.
I have watched many youtube videos on the OSI layers, and this is my favorite one. This really gave me a good understanding of the OSI layers in a real world scenario. Explained simply and gets the points across. Just great!
Your Channel is a gem. I landed on this channel searching about the difference between proxy vs reverse proxy, ended up watching at least 10 videos as of now. Though I am a frontend engineer, still I feel everyone should have this basic networking knowledge.
First ever I came across the concept of OSI was in 3rd year bachelors and it's been 4 years since. Today is the first time I can say that I understand the whole damn thing and what each layer does. You are a legend Hussein.😁
Omggg where was Nasser in 2015 when I was pursuing my undergrad?! Computer Networks made me cry as a subject just because I could not digest the huge amount of information bombarded at us during the coursework. This info along with the diagrams, is gold 💯. Really helped me understand the OSI model - something I thought would never be possible (coz I tend to get lazy when things stop making sense or when I'm unable to visualize what is happening)!!! Thank you Nasser 💯❤
I don't think I've ever heard any explanation of any topic to be this much interesting and fun ever! Thanks a lot! I wish I could learn every other subject from you...
thank you sir.. you just explained something in a great and easy way that i couldn't understand though out my computer networks class. Now i am less scared of the subject
My god!! I’ve been trying to understand OSI from so long but theory sucks!! Glad that i just found your video! First time i got entire thing cleared ! Great work
ohh god i am so happy i found ur vidoes and so excited to watch all ur videos......i swear i am gonna binge watch ur videos.....and thanks a lot to you for making such amazing videos........sending lots of love to you.......thanks man
Thank you for the explanation Hussein! I was first exposed to the OSI layer through work when dealing with CAN networks in industrial vehicles (EE background), and have never found a resource that would help me create a solid mental model until now. This is it. The example is great, and it explains OSI's layers and main concepts really well.
@hnasr I've been always seeing osi model from bottom(network engineer view) Now that I'm seeing it from top( software engineer view) a lot of stuff becomes more clear. Great work brother, keep up the hard work😊❤
Packet in Layer 3 encapsulate in Layer 2 frame by adding source MAC address and destination MAC address(in case of Ethernet) and add some FrameCheckSequense. Hussein, in your explanation 2 packets of network layer divided into 3 frames of data-link layer, I think its not true. If IP destination in same LAN with source, Then destination MAC equals MAC of destination host, in other cases Destination MAC will be MAC of host with IP equals default gateway, this mac will be known by ARP request about IP of host in same LAN or IP of default GW. Maybe this is an unnecessary explanation for a software engineer, but in fairness I wanted to write about it. Thank you for good content.
Electricity does not have a direction (Omg) I learned something new today. Thanks for your video. you really helped me to understand OSI model finally :D
no I am not yawning, its interesting how you are giving related knowledge also with the topic information. keep it up this way, i like it thank you for this informativve vedio.
Very well explained if it comes to particular layers, what happens in every layer, however the last part of video seems to be a bit too oversimplified for me. I think you should exemplify how data travels from one device to another with more 'tricky' network topology. Also I think you should distinct network devices such as switch, router and firewall, because in fact standard SOHO (small-office-home--office) 'router' consist of those 3 devices combined into one box. Of course then the video wouldn't last 25 minutes, this is knowledge that need some time to be explained :) Anyway, I love your content, your channel is really good place for backend engineers. Greets from Poland!
@Hussein absolutely nice explanation. The thing about bits converting to light is an eye opener. Just makes it so clear to connect the dots now. Thanks buddy!
Hey Hussein, Your videos are very didactic and helpful, thanks for that. However layer 2 (switches ) breaks the domain of collision of a datagram. In the picture what looks like a router includes a switch capability and therefor a datagram would not broadcast to all the devices in it’s network. Please let me know if I miss understood your explanation. Thanks again.
Thanks Alberto you are absolutely correct. The router (switch to be exact) will route datagrams to the specific mac addresses based on the port. I am not sure how this works in WIFI/4G,
Nice comment because I was a bit confused about the fact that every data is send to everybody all the time. Switches and routers doesn’t make sens if I follow your explanation but thanks to discuss it in the comments. Broadcast data will arrive to everybody.
Hey Hussein. Thank you so so much for this wonderful lecture. I feel like something has been unlocked inside my brain haha. A quick question regarding this transmission of data between internal servers. You have demonstrated the network travel from a device C to device D, all connected to a private router. Could you please say in short what happens when I connect an external ip of a server from one of my devices, like say for example 237.65.42.121 is some external ip and Im connecting there. What would happen at that point regarding the public wifi? Im asking this question because now the destination device is not within the public wifi connected devices and is somewhere at the other side of the world. At this point how would the other guys were able to see the data. Again Im a bit confused as the example was solely relied towards a LAN and not a WAN. Apologies for this long message and thank you so much once again. I started my career as a full stack dev 3 years back but never knew there existed such depth in backend. I just started watching your backend engineering playlist and its so so fun to learn all these nuances behind. Feels so satisfying haha.
Thank you Sundeep for your comment! Glad you enjoyed the video and found it helpful. As for your question, I believe you will like this detailed video on what happens when you go to google.com th-cam.com/video/dh406O2v_1c/w-d-xo.html
@@hnasr Tons of thanks for that redirect. Let me summarize what I learnt from the video. If the connection is between a LAN network, (10.0.0.1 to 10.0.0.5) then it just goes directly to it, by asking each device "hey are you 10.0.0.5?". But if that is a WAN network, then our router would be the medium (gateway), between us 10.0.0.1 turned to some external IP of 44.3.28.12 and the external server of IP 237.65.42.121 Now the crux of my understanding is, while we are going through the router, that is the reason the other connected devices still know what we are asking, coz now we are technically still bound with our router's IP. Please correct me if I am wrong. I am a bit noobie in this department, but Im trying to learn haha.
Hi Hussain Thanks for making such a wonderful video on most confusing topic ever, Now I understand how does this OSI model works on higher level, Can you also please explain how does three way handshake work's on context with OSI model, And how does it maintain the session between client and server in context of OSI model.
Hey guys in minute 16:00 I forgot to mention this is a WIFI configuration not wired .
so all devices within range will receive the those packets since they are in radio vicinity and drop them if they are not intended for them.
if that was wired than the router (acting like a switch) will be smart enough to only forward to required device by identifying which port it is connected to.
I was really confused until i saw this comment. Thanks! However, I do have a question, in a network of only wired computers, how could someone listen for packets? If the router is only sending the packets to the intended recipients, then I don’t see how someone could sniff packets unless they had access to that router. Basically, would tcpdump or wireshark work in a completely wired network?
Yup. At 16:00 i paused the video came to comments section.
in case of wifi, doesn't the client set the destination as a router(which is a default gateway for it) at some layer and then the router directs the packages to the server? So, basically, the server receives the package twice: first time from the client and second time from the router; but first package it drops at some lower layer as it doesn't know yet that it is the destination of that packag. Or in case of wifi, the router even doesn't takes a place in client-server communication? Why I'm asking, becasue at the moment when client sets the destination at data link layer it doesn't know what media will be used to transfer the data(wifi or wired connection) so it sets as a address its gateway
that's what is was wondering shouldn't router/switch do it for you
Great video.
I feel like I want to quit my job and spend a few weeks just studying your backend topic videos. Really interesting stuff. I was even able to explain to my wife why she can't access homebanking in a starbucks.
Same way I feel!! So sad I discovered Hussien late!
I quitted my job and and I discovered this channel... I know that feeling, i think I need at least one month to watch all the videos and after that maaybe get another job 😆
@@dicksonchibuzor2792 seriously
exactly. I was also thinking to take a break from my job to deep dive into backend.
i am also doing it
Guys here are some jump codes to help you navigate, 2:15 public vs private ip address, 4:00 Application Layer, 5:30 Presentation Layer, 6:20 Session Layer, 7:20 Transport Layer, 9:20 Network Layer, 11:20 Data Link, 13:00 ARP protocol, 14:00 Physical Layer, 19:00 Why you shouldn’t connect to public WIFI
I enjoyed making this video!
I have a lot of question. Would you help me?
Thank you for this great tutoriol❤
"Intended for you as a device, but not as an application" - Perfect way to explain the way the router works when you make a request to external network 👌
Hi Hussein, thank you for making this video. I just want to clarify one thing. At 16:20, you say that the stream of bits that are being sent from the client will go into server 1,2,3,4..etc essentially to all servers. This is not correct. I'm a software engineer working in networking domain, and in networking the direction of packets is either "unicast" (meaning it's directed to one client only), multicast (meaning it's directed to two or more known clients), or broadcast (meaning the traffic is directed to any machine that's on that network). In your case, since the server is hosted on machine C, the data is directed to that machine and it will only go to the router first and then to that machine regardless of the medium used to transfer the packet (Ethernet or WiFi). If the stream of bytes were transferred using WiFi, you are right in that the data will be broadcasted all over the place using radio waves but only the router will be able to interpret those packets, because that's how WiFi works, and the other machines (even if they have a WiFi receiver) will not be able to decode the packet and see the bit streams. Just wanted to point this out to clear any confusion. Thanks for making these video. They're very useful and informative.
I looked in the comments specifically for this
but how does physical layer know that the server is hosted on C ? How does it decide to route to C at physical level ?
@@devarsdk the physical layers knows that this is for him, and he then checks to what local ip he needs to redirects it request and then it broadcast the wave again and that;s for C
Hi, this context helped me a lot. Sometimes I see the term anycast, has something to do with this. Is it the equivalent to broadcast?
@@devarsdk You need to learn about ARP protocol. I think that will solve your problem
Summary of:
OSI (Open Systems Interconnect) model, from a software Engineer's view (Please correct me if I'm wrong):
Layer 1 Physical
This is the physical layer, in which 1 and 0 data bytes can be sent as electric signals, wifi, or light via "the wire"
Layer 2 Data Link
These are the separation of the data bytes into frames.
Notably, the frames will identify the source and destination MAC addresses of the devices' network card.
Since electrical signals travel in all directions in a network, the data frames reach all devices in the network.
Once the data frame is able to identify that the device is not the intended destination, the frames drop.
In an unsecured network, this is where a malicious application can choose to not drop the frames, and steal the data.
Layer 3 Network
Once layer 2 is done, it generalizes the frames from MAC addresses to IP addresses.
Layer 4 Transport
This tranport layer further generalizes the network layer IP address into source and destination ports.
Layer 5 Session
Since there may be several TCP connections to one server at a time, with identical packet information from layers 1 through 4, we need a way to distinguish the session by ID to tag it.
Layer 6 Presentation
This is where the resource might be secured/encrypted with HTTPS/TLS by scrambling the HTTP request string.
I didn't know HTTPS encrypted anything. I thought it was only a way to identify the true identity of a website.
Also, encryption might be accomplished via VPN.
At this step, if the data is encrypted, the model decrypts the information to reach step 7.
It might be possible that a malicious attack to steal data can be avoided by encrypting.
"This is where you can get screwed if you are on public wifi...people can sniff your data."
Layer 7 Application
This is where a client device makes a request to a server device, such as a GET request.
This request contains a whole bunch of information, such as headers, cookies, content-type headers, etc, which is summarized into a string, so the string can participate with the rest of the OSI models as byte data.
Andres! Amazing summary thanks for taking the time to compile this. It would be nice to separate the summary based on the sender vs the receiver . Thanks for being a fan of this channel :)
Damn. Nice one. 👍Anyway you could summarize quantum mechanics too?
@@praiseokonta8879 😂
@@praiseokonta8879
Lol 😂
Read this after watching. Great summary to recap everything 👏👏👏👍
It is a dry topic, but somehow even with your thick accent and minimalist presentation style, your charisma makes this video a joy to watch. Seriously.
I have watched many youtube videos on the OSI layers, and this is my favorite one. This really gave me a good understanding of the OSI layers in a real world scenario. Explained simply and gets the points across. Just great!
Your Channel is a gem. I landed on this channel searching about the difference between proxy vs reverse proxy, ended up watching at least 10 videos as of now. Though I am a frontend engineer, still I feel everyone should have this basic networking knowledge.
❤️ thank you Deepak! Welcome to the channel
First ever I came across the concept of OSI was in 3rd year bachelors and it's been 4 years since. Today is the first time I can say that I understand the whole damn thing and what each layer does. You are a legend Hussein.😁
Congratulations!!
Your content has reached India. Now, sit back and watch your channel grow.
I wish i could understood the Beauty of OSI model a year before. Really awesome video ...
Omggg where was Nasser in 2015 when I was pursuing my undergrad?! Computer Networks made me cry as a subject just because I could not digest the huge amount of information bombarded at us during the coursework. This info along with the diagrams, is gold 💯. Really helped me understand the OSI model - something I thought would never be possible (coz I tend to get lazy when things stop making sense or when I'm unable to visualize what is happening)!!! Thank you Nasser 💯❤
Your humour lines in between your awesome teachings are really nice and engaging.
Thanks for a refresher and keep it up!
At last i laughed when the web server got the GET request😉😉😉........Awesome explanation
I am binge watching the backend engineering playlists. Awesome content. Keep up the good work! :)
Enjoy!
Hey Hussein!
You really rocks!! It's amazing how clearly your explanations are about complex stuff!
Congrats!
I don't think I've ever heard any explanation of any topic to be this much interesting and fun ever! Thanks a lot! I wish I could learn every other subject from you...
This was hugely helpful for me to get into cybersecurity.
thank you sir.. you just explained something in a great and easy way that i couldn't understand though out my computer networks class. Now i am less scared of the subject
Lakshaya Sood really happy I could help! Best of luck on your study 📖 cheers!
The best video ever made to explain OSI
Thank you Aniket!
i just addicted to this channel.
So now I can explain to non-techie people why you shouldn't connect to a public wifi network!!
Great video 💯
I have been listening to your videos for days. I can finally understand this stuff. Thank you so much!
❤️❤️❤️
My god!! I’ve been trying to understand OSI from so long but theory sucks!! Glad that i just found your video! First time i got entire thing cleared ! Great work
A huuuuuuuuge plus from me. This is a best explanation of network communication I have ever seen in my engineer career.
A gem in tech world. Gracias brother.
very very very underrated video, The best explanation I have ever seen on youtube sir.Thank you for making these kinds of videos 🙏🙏🙏🙏🙏🙏
I am Definitley going to use this approach to explain the concept to people
Thank you for this great explanation. After 8years finally I understood this model.
I have used Wireshark before, and the way you introduce it in the video makes me try to correlate every technology that I am using as a developer.
Best OSI explanation ever!
Literally after going through the video I felt like I have achieved a lot today already. Thanks you.
I am soo glad i found your channel right before my Amazon interview ♥
the best explanation about how packet sniffing and interception works. thanks for this!
"I was in university 10 .... Ohh no maybe 20 years ago ... Damn I'm old" 😂😂😂
But you make awesome tutorials ... Keep it up !
Apoorv pandey 😂 Thanks 🙏 glad you enjoying the content
😂😂😂😂
ohh god i am so happy i found ur vidoes and so excited to watch all ur videos......i swear i am gonna binge watch ur videos.....and thanks a lot to you for making such amazing videos........sending lots of love to you.......thanks man
Sending love ❤️ back
This video gave me a great understanding of the OSI and is a fundamental part of my progress in IT! Great work!!
Sir, you make evrything seems as simple as the waterflow , thank you so much for all of your efforts
This is explained really well and it is abstraction done right for beginners. Good job and thank you!
Thanks! Glad you enjoyed the video cheers!
Finally i managed to understood OSI. Thanks Nasser.
Best explanation of OSI I've ever seen (and I've seen lots of them)
Hey Nasser, This is the best explanation I have seen for OSI model. Thanks for the great video.
The "Yayy" at 4:58 had me weak 😂😂. Love your content man.. you give direction to aspiring backend engineers. Please make more 💯
Thanks Hussein! These videos are brilliant. I wish I had discovered them earlier.
No worries! glad they are helpful!
Finally found the perfect video after searching for long. Thanks!
19:00 Now it makes sense why people try to use Wireshark to capture data in public wifi network. thanks !
Thank you for the explanation Hussein!
I was first exposed to the OSI layer through work when dealing with CAN networks in industrial vehicles (EE background), and have never found a resource that would help me create a solid mental model until now. This is it. The example is great, and it explains OSI's layers and main concepts really well.
Very useful, entertaining description of the OSI Model. Now I understand more about why it’s important to encrypt data in transit.
literally the best explanation fr
Thank you man for this. I wish you know how long i have been stuck in the osi plateau. It just clicked
I am able get this since I am from networking background. don't know if begineers would get this. But good content for people with background
@hnasr
I've been always seeing osi model from bottom(network engineer view)
Now that I'm seeing it from top( software engineer view) a lot of stuff becomes more clear.
Great work brother, keep up the hard work😊❤
Dude, this is GOLD.
You are just great . the way you explain and keeping things as simple as possible make your tutorials so interesting .
I never really understood this in college too and now I do. Thank you!! :)
People like you are who actually run this world 😔
Packet in Layer 3 encapsulate in Layer 2 frame by adding source MAC address and destination MAC address(in case of Ethernet) and add some FrameCheckSequense. Hussein, in your explanation 2 packets of network layer divided into 3 frames of data-link layer, I think its not true. If IP destination in same LAN with source, Then destination MAC equals MAC of destination host, in other cases Destination MAC will be MAC of host with IP equals default gateway, this mac will be known by ARP request about IP of host in same LAN or IP of default GW. Maybe this is an unnecessary explanation for a software engineer, but in fairness I wanted to write about it. Thank you for good content.
Electricity does not have a direction (Omg)
I learned something new today. Thanks for your video. you really helped me to understand OSI model finally :D
Thank you so much for doing this, I have watched a lot of your video :3
Great! Thanks for your comments very happy I could help. Let me know what other software engineering content you would like me to make 😊
no I am not yawning, its interesting how you are giving related knowledge also with the topic information. keep it up this way, i like it thank you for this informativve vedio.
Thank you i wish i found your channel much eariler...
Thanks ! Your here now and thats what matter. enjoy the content ! And tell me what should I make next .
Thanks for another good explanation bro, as a web developer your videos help me lot because they are basic and very understandable.
Eren Sertkaya thanks Eren, happy I can help and we all have room to always learn more! Its an infinite field
Gosh, brilliant deliver of dry OSI theory. Thanks!
" OSI is Open Systems Interconnect, I don't expect you to remember it"
Me: "meh I think I will"
*midway through the video*
"what's OSI again"
I relate too much to this 😂😂
thank you so much, you amazingly simplified a complex topic that I did not fully understand when I was in university ❤️❤️❤️
I love this guys accent. Sounds like Shrek is giving a tech training. It's awesome and hilarious
Wow I never even noticed. I kinda thought he resembled the Indian guys with hypercam2 from 2008. Which is a good legacy to hold up to.
Very practical examples, excellent as always
You are just insane buddy....amazing.....thank you millions
Dear Hussein, awesome video. I learned a lot and loved and laughed with every bit of your explanation!
Hussain, you are the BEST !!
Very well explained if it comes to particular layers, what happens in every layer, however the last part of video seems to be a bit too oversimplified for me. I think you should exemplify how data travels from one device to another with more 'tricky' network topology. Also I think you should distinct network devices such as switch, router and firewall, because in fact standard SOHO (small-office-home--office) 'router' consist of those 3 devices combined into one box.
Of course then the video wouldn't last 25 minutes, this is knowledge that need some time to be explained :)
Anyway, I love your content, your channel is really good place for backend engineers.
Greets from Poland!
I really enjoyed watching this, brilliant explanation. Thanks❤
@Hussein absolutely nice explanation. The thing about bits converting to light is an eye opener. Just makes it so clear to connect the dots now.
Thanks buddy!
Thank you for explaining so well. Thank you for your efforts
it really is cool to finally understand what's happening. thanks a ton!
You are amazing. Thank you brother. I appreciate you. Please keep making more
Thanks Eric!
Thanks a lot Hussein for sharing this. This is really amazing and the way you have explained is so awesome.
Perfectly explained
Really a great understanding i have got today😇
Thank you for making this so simple to understand!
Hey Hussein, Your videos are very didactic and helpful, thanks for that. However layer 2 (switches ) breaks the domain of collision of a datagram. In the picture what looks like a router includes a switch capability and therefor a datagram would not broadcast to all the devices in it’s network. Please let me know if I miss understood your explanation. Thanks again.
Thanks Alberto you are absolutely correct. The router (switch to be exact) will route datagrams to the specific mac addresses based on the port. I am not sure how this works in WIFI/4G,
Nice comment because I was a bit confused about the fact that every data is send to everybody all the time. Switches and routers doesn’t make sens if I follow your explanation but thanks to discuss it in the comments. Broadcast data will arrive to everybody.
this is pure gold
Excellent explanation even compared to the university course. Thanks so much and all the best Hussein.
i'am proud of you Hussein
u r a pride for all the Arabic and Muslim world
Good stuff man finally demystified for a dumbo like me
Thank you sir. Really enjoyed this journey of data. ❤
Thanks Shovon! Its impressive right? Seeing how data flow
The part about "electricity has no direction" is so cool 🤭
Thanks..this is the best channel
This video is great. Clear explanations. Thanks for making it 👍👍
Thanks for this beautiful video!!
Thanks 😊 are you going to dig deeper in this topic?
Hey Hussein. Thank you so so much for this wonderful lecture. I feel like something has been unlocked inside my brain haha.
A quick question regarding this transmission of data between internal servers. You have demonstrated the network travel from a device C to device D, all connected to a private router. Could you please say in short what happens when I connect an external ip of a server from one of my devices, like say for example 237.65.42.121 is some external ip and Im connecting there. What would happen at that point regarding the public wifi? Im asking this question because now the destination device is not within the public wifi connected devices and is somewhere at the other side of the world. At this point how would the other guys were able to see the data. Again Im a bit confused as the example was solely relied towards a LAN and not a WAN. Apologies for this long message and thank you so much once again.
I started my career as a full stack dev 3 years back but never knew there existed such depth in backend. I just started watching your backend engineering playlist and its so so fun to learn all these nuances behind. Feels so satisfying haha.
Thank you Sundeep for your comment! Glad you enjoyed the video and found it helpful. As for your question, I believe you will like this detailed video on what happens when you go to google.com
th-cam.com/video/dh406O2v_1c/w-d-xo.html
@@hnasr Tons of thanks for that redirect. Let me summarize what I learnt from the video. If the connection is between a LAN network, (10.0.0.1 to 10.0.0.5) then it just goes directly to it, by asking each device "hey are you 10.0.0.5?". But if that is a WAN network, then our router would be the medium (gateway), between us 10.0.0.1 turned to some external IP of 44.3.28.12 and the external server of IP 237.65.42.121
Now the crux of my understanding is, while we are going through the router, that is the reason the other connected devices still know what we are asking, coz now we are technically still bound with our router's IP.
Please correct me if I am wrong. I am a bit noobie in this department, but Im trying to learn haha.
Loved your way of teaching Hussein Sir ❤️ Never stop what you're doing. You are great at it.
Thank you 🙏
Very easy to understand and helpful. Thank you!
Thanks for this amazing video, How does the destination device decrypt?
wonderful animations Nasser, Kudos.. thanks a bundle.
Feynman technique at its best
wonderful video Nasser!!!
Hi Hussain
Thanks for making such a wonderful video on most confusing topic ever, Now I understand how does this OSI model works on higher level, Can you also please explain how does three way handshake work's on context with OSI model, And how does it maintain the session between client and server in context of OSI model.
Thanks! Yeah thats a great topic! I haven’t discussed on my channel
@@hnasr Am really waiting to see that video , thanks a lot for all your effort am really enjoying it.
Well done sir. Thank you👍.