Just in case anyone else can find it useful I remember the difference between TCP/UDP by thinking of the T/U as Tethered/Untethered instead of transmission/user. Helps me remember TCP is connection oriented and UDP is connectionless
I had to spend quite a while on understanding what the connection vs connectionless really meant. Once I did, this comment made so much sense! I don’t think I’ll get confused again.
Dude you and me both. What’s bad for me is that I totally know what he’s talking about but I have zero understanding as to what he’s talking about. I’ve heard these topics for so long but I’ve just never grasped the concept or put it to use at all in my life.
Yeah I really don't like this house and boxes combo explanation. I read the text book and it made sense, but I keep getting lost because he goes from talking about tcp/udp to houses and shit and it's hard to follow all that he's saying. I wish he'd just explain what it is simply, and then go into an analogy to help you visualize it.
Here's how I remember the idea of IP addresses and port numbers. Every apartment building has an address, every computer has an IP address. Every apartment in that building has a number, every application has a port number. Hope it helps 👍
That's exactly the right way to think about it. the Transport layer sits on top of the Network layer, so it relies on the Network Layer. The reverse is not true! So we can deliver to the apartment building without knowing that individual apartments have numbers, but we can't deliver to a specific apartment without knowing about the existence of the apartment building
Thanks that really helped a lot! But just a quick question if you or anyone can answer. What exactly is an application? Cause to my knowledge(very little/beginner) an application is something like Discord, Microsoft Excel, Steam, Visual Studio Code, Google Chrome etc. But does the word "application" , in the IT sector, refer to stuff like windows administrative tools, active directory, Settings in windows, file explorer etc. So how broad exactly is the term "applications" used for?
man ive never felt like i was missing out on a job so confidently until i started watching this play list, 90% of the info is stuff i knew. thank you for helping me realize
I genuinely don't believe I would've passed my certification if I didn't find Professor Messer. I am forever grateful and all of this FINALLY makes sense to me. Thank you thank you thank you for breaking it down and making it more easy to digest. :)
This is the first time ive encountered someone who explained IP similiar to how I understand it.... When it comes to network addresses and end hosts, I see the network address as a neighborhood, and the individual IP addresses are the individual houses in the neighborhood
This is really well done, I'm happy I found professor messer on my way to the comptia a+ The truck example for IP really helped visualized the inside happenings of IP. Thanks professor
This is definitely one of the more difficult videos to grasp, even as someone who has hosted home servers before. I'm sure now that I've gone through it once in detail I can watch a few more times and have a very solid understanding.
So this has to be updated every 3 years? If I smash this exam in a couple weeks it’s going to be good for a year then I have to do it again. Sigh. I’ll do what I have to do. Thank you for making these videos for free. You are a hero Professor Messer.
In 7:38 you say that DHCP is responsible for making sure informatins has been recieved by the other side but that contradicts the UDP rule that DHCP follows. Am I missing something - anyone can help?
DHCP is its own protocol. It doesn't have to follow the same process used by any other protocol, including UDP. If UDP isn't going to provide the functionality, then it's up to the higher layer protocols to do it themselves.
OK this chapter is the one that I'm really struggling with conceptually. Can someone tell me if I'm understanding this properly? For an example. When I click "play" on this video. I am the "client." The data of my click is packed into a moving truck and sent through my Ethernet cable to RUclips's server, where it's unpacked, and then the video plays. Right? But then is RUclips's server also sending me the client the data of this video?
You are the client, RUclips is the server, and the video data RUclips sends to you is the data being talked about. When you press play here on your screen, your application sends a data request to the YT server. Then YT packs the data and sends it to you. How is the data packed and sent? That is what this lecture covers. Now how the data is specifically packed and sent for specific single applications is out of the + of this course. As you see in this video, you'll learn how data packaging and transfer happens at a general level. Real life analogy : 1. You have a painting to transfer - This is your application data. 2. You wrap it in a box and name with box with a marker for protection and identification - This is TCP / UDP encapsulation (adding a TCP / UDP header). 3. You put the box in a truck and you mark the truck with the source and destination address - This is IP encapsulation. The truck is the IP packet, and this is done by adding an IP header to the data. 4. The truck runs on the road to reach the destination address - This is the data actually travelling the physical path. Be it through the medium of physical wires, or radiowaves (wireless). The road here symbolises the physical connection between the host and the client.
Obviously, the painting example is just a comparative analogy and not totally accurate, but you get the idea. Referring to your initial comment, when you click 'Play' on your phone, you request data from RUclips, and thus you become a client. Correct. Don't think of you sending a click to RUclips server. That is not important. What is important is that you request data (video) from YT, and thus YT becomes host. And you become client. And then the whole TCP/UDP - IP cycle starts for each IP packet of data YT sends to you.
@Nada, go to POWERCERT on RUclips and watch a video of them explaining this. They make it so easy to grasp with their animation. You can use them to supplement professor's videos.
7:40 See i thought that DHCP as it uses UDP has no way to verify if information has been received like TCP does. Does the external application pick up on the error and DHCP is just simply a way of resending?
Hopefully someone can answer this for me. at 18:00 , UDP/5004 is used as an example for a VoIp server but I thought previously in this video he explained that ports above 1023 are Ephemeral ports that are real time ports typically from the client? so why or how is that server's port 5004? edit : was this just an example of when he said most servers are non-ephemeral but not always? or is there more to this that I'm missing?
The ranges used for an ephemeral or non-ephemeral block of port numbers are common guidelines, but they aren't strict rules. As you've already seen, some services use whatever port number they'd like.
Hello Professor, at the beginning I talked about that DHCP follows the UDP protocol and the UDP protocol when it sends data does not give any attention whether the data is complete or incomplete, and therefore in the minute 7:37 I spoke that DHCP is responsible for verifying and retransmitting information, can anyone explain me this?
Probably best to trust the expert on this one. From wikipedia: The DHCP employs a connectionless service model, using the User Datagram Protocol (UDP). ... The DHCP ensures reliability in several ways: periodic renewal, rebinding, and failover. DHCP clients are allocated leases that last for some period of time. Clients begin to attempt to renew their leases once half the lease interval has expired. They do this by sending a unicast DHCPREQUEST message to the DHCP server that granted the original lease.
Maybe it's because I've gamed my whole life but the port 25565 is all I think about with TCP/UDP. Hosting Minecraft servers for my friends as a 12 year old really came in clutch.
I have been confused about IP Address and Ports. Watch other videos too, but this was really the best explanation, in my opinion. I can retain the information much better too. Maybe it's his voice 😂
So much! I had to pause and go absorb the entire OSI model to even make sense of this video. Glad I did tho because I had no idea OSI was a basic framing of the entire concept of IT
Began studying literally this week. First few videos I'm like :D this is interesting, oooo I know this already, maybe getting into IT is for me! This video I'm like :O >:( :( I'm so lost lol.
This is an amazing course and I'm loving every second of video, but I'm commenting here completely mind blown that you've used a picture of my village, Veli Losinj, as the banner for your presentation :') Small world!
Question, when explaining UDP, with no confirmation that data has made it to the other side, why does then DHCP using UDP protocol become responsible for resending the data? What did i miss
ITF+ would be more for people unfamiliar with technology and its terms. This, as far as I understand, are for those familiar with such things. A+ is for people who have or can use a tablet, a computer, know what a word processor is, etc. ITF+ would be for those that don’t use tech.
Also, if you have a study guide book with you, you will easily recognise those terms and it would be easier to for you to follow the video as Professor Messer is following exactly the same structure objectives.
Question: So hypothetically speaking regarding ports and applications lets say you have a server dedicated solely to FTP (I'm aware servers could contain VM's to house multiple different services) would that server only operate out of port 20 & 21?
Hi, the amount of content in your channel is amazing. As a beginner myself I can't help feeling overwhelmed. I see so many Comptia courses in your channel. Where should I start? Thanks!
@@kingjamir2135 In fact yes! Just done ny first week. No A+ needed here in UK , to be honest they don't really hold a lot of weight here except CCNA. Net+ and sec+ can be useful just depends on company.
I definitely understand the concept. But what im hung up on is how the computer filters out all the packages. Maybe im getting ahead of myself but in a situation where there are 1000s of phones accessing a cell does the "driver of the bus" have to drive to each phone and get rejected 1000s of times before finding the right 1? And then what? Its just really fast morse code so even if the phone unlocks to receive data its just going to get random date from all the different transmissions. Only thing i can think of is its either only 1 signal is sent at a time and switches very fast or its a specific radio frequency the phone looks for that has its IP being broadcast
aaah, i tried to take the test before I had studied a while ago, and while I did pretty good I got almost none of the Networking sections because I simply didn't know what a lot of it was called or what they did. Unfortunately, that caused me to fail (which is why I'm here), but these videos are really good at explaining the exact parts that I need to study for the retake. Thanks!
My question is why ports on the sending side are randomly picked. I thought the IP address was fixed so why is the port able to change? any explanation would be helpful
i have confidence in ep 1-8. im trying to rewatch and trying to fully grasp an understanding of ep9-10 and im having difficulty. Anyone have any tips? Ive rewatched ep9/10 like 4/5 times now and I cannot fully grasp the entirety of the videos.
not sure if this is a dumb question but ill ask anyways. at 15:58 it says the web server and the email server is using TCP and VoIP is using UDP. My question is what types of services would you use for TCP and UDP?
Im guessing UDP is more like talking on a phone. It sends you voice and even if the other person cant hear you because of their service. Udp will just keep sending the other stuff you said after. And im assuming tcp is like a text message i guess. If you send it and it fails you can just send it again. If i am right i hope someone can let me know. Im still learning.
TCP for integrity sensitive application data at the cost of latency. E.g. bank transactions. UDP for latency sensitive application data at the cost of integrity. E.g. mmorpg/online game data.
@@kingjamir2135 yes this is correct. the example uses VOIP for UDP because that would require some help to ensure the data is properly transferred. With VOIP, this can be like calling a friend, if they can hear you then you know the information was transferred by them replying to you.
I think you are correct. DHCP is not responsible for checking if we received, but the device that is being assigned an IP by dhcp will know when it does not get all the information. The device will tell the DHCP service that it did not get the IP addrr, and DHCP will start its sending of data again. This may sound like tcp, but in DHCP my device will not send ACK (acknowledgments) for EVERY piece of data, and will not let DHCP know that everything is good to go. DHCP sends all the data with the assumption that I will receive all the data and doesn't care further. If you have downloaded a torrent, your are a peer receiving udp data from all active seeders that are connected to you. And when you finish the torrent and leave it running, you begin sending chunks of data to any leechers your torrent client is connected to.
Just in case anyone else can find it useful I remember the difference between TCP/UDP by thinking of the T/U as Tethered/Untethered instead of transmission/user. Helps me remember TCP is connection oriented and UDP is connectionless
ty bro
I had to spend quite a while on understanding what the connection vs connectionless really meant. Once I did, this comment made so much sense! I don’t think I’ll get confused again.
Appreciate it
That makes sense thank you
hilariously this actually is more confusing for me lol, but I already understand it so I'm not worried, just refreshing my memory
I don't think I've ever gone from "yeah I understand everything you're saying" to "oh my gosh I have no clue" so quickly.
Dude you and me both. What’s bad for me is that I totally know what he’s talking about but I have zero understanding as to what he’s talking about. I’ve heard these topics for so long but I’ve just never grasped the concept or put it to use at all in my life.
port, port, portport, portportport, port
You're not alone! I've been taught this topic several times and i'm just now starting to understand
Yeah I really don't like this house and boxes combo explanation. I read the text book and it made sense, but I keep getting lost because he goes from talking about tcp/udp to houses and shit and it's hard to follow all that he's saying. I wish he'd just explain what it is simply, and then go into an analogy to help you visualize it.
@@nootnoot-2 agreed
Here's how I remember the idea of IP addresses and port numbers. Every apartment building has an address, every computer has an IP address. Every apartment in that building has a number, every application has a port number. Hope it helps 👍
Helped a lot. Thank you!
Ohhh so helpful!
That's exactly the right way to think about it. the Transport layer sits on top of the Network layer, so it relies on the Network Layer. The reverse is not true!
So we can deliver to the apartment building without knowing that individual apartments have numbers, but we can't deliver to a specific apartment without knowing about the existence of the apartment building
Thanks that really helped a lot! But just a quick question if you or anyone can answer. What exactly is an application? Cause to my knowledge(very little/beginner) an application is something like Discord, Microsoft Excel, Steam, Visual Studio Code, Google Chrome etc. But does the word "application" , in the IT sector, refer to stuff like windows administrative tools, active directory, Settings in windows, file explorer etc. So how broad exactly is the term "applications" used for?
Thank you so much for this comment!
man ive never felt like i was missing out on a job so confidently until i started watching this play list, 90% of the info is stuff i knew. thank you for helping me realize
Agreed !
Dew It! Come to the Dark Side!
I just sat through an entire 9-5 class to realize this
Professor Messer - the undisputed G.O.A.T.
I genuinely don't believe I would've passed my certification if I didn't find Professor Messer. I am forever grateful and all of this FINALLY makes sense to me. Thank you thank you thank you for breaking it down and making it more easy to digest. :)
多謝！thank you for the video! its really helpful!
This is the first time ive encountered someone who explained IP similiar to how I understand it.... When it comes to network addresses and end hosts, I see the network address as a neighborhood, and the individual IP addresses are the individual houses in the neighborhood
I dont consider myself new at this. Yet i keep coming back to review material. So thank you for what you do Sir.
reviewing the fundamentals every once in a while really helps you expand your knowledge into the more advanced
Great piece out there for some of us from Africa. This job you are doing is Godly. keep it up. God bless you, Prof.
This is really well done, I'm happy I found professor messer on my way to the comptia a+ The truck example for IP really helped visualized the inside happenings of IP. Thanks professor
Good luck brother.
I’ve always had issue with figuring out ip addresses, this made sooo much sense to me. I love finding people who can make things so clear to me
Ok, this is my rewatch of playlist and I finally get it. This playlist is just so good
professor messer = G.O.A.T.
Thanks for this clear and sharp explanation .... the truck and house delivery simile was brilliant 🙏🏼🙏🏼
It’s a good metaphor but I had to replay it several times lol, I’m a bit dumb (but I also listen to these at work)
@@yomejjuan IP/TCP is just really complicated to the uninitiated, you really have to think about it even with good metaphors to really get it
I’ve probably learned this portion 3 times and this is my first time throughly understanding 😂
This is definitely one of the more difficult videos to grasp, even as someone who has hosted home servers before. I'm sure now that I've gone through it once in detail I can watch a few more times and have a very solid understanding.
Wow, I've learned so much in 18 minutes thats crazy!!! This high quality content!!!
Simply put… Professor is the goat
100%
this is so clear. always thou networking was my least known subject but you make it so simple to understand thank you professor
So this has to be updated every 3 years? If I smash this exam in a couple weeks it’s going to be good for a year then I have to do it again. Sigh. I’ll do what I have to do. Thank you for making these videos for free. You are a hero Professor Messer.
Once you are certified, your certification is good for three years. Changes to the exam version do not change the status of those already certified.
In 7:38 you say that DHCP is responsible for making sure informatins has been recieved by the other side but that contradicts the UDP rule that DHCP follows. Am I missing something - anyone can help?
DHCP is its own protocol. It doesn't have to follow the same process used by any other protocol, including UDP.
If UDP isn't going to provide the functionality, then it's up to the higher layer protocols to do it themselves.
@@professormesser Thank you Professor that makes sense !
Excellent. This video on ports on a network helped broaden my understanding of them.
OK this chapter is the one that I'm really struggling with conceptually.
Can someone tell me if I'm understanding this properly? For an example. When I click "play" on this video. I am the "client." The data of my click is packed into a moving truck and sent through my Ethernet cable to RUclips's server, where it's unpacked, and then the video plays. Right? But then is RUclips's server also sending me the client the data of this video?
You are the client, RUclips is the server, and the video data RUclips sends to you is the data being talked about. When you press play here on your screen, your application sends a data request to the YT server. Then YT packs the data and sends it to you. How is the data packed and sent? That is what this lecture covers.
Now how the data is specifically packed and sent for specific single applications is out of the + of this course. As you see in this video, you'll learn how data packaging and transfer happens at a general level.
Real life analogy :
1. You have a painting to transfer - This is your application data.
2. You wrap it in a box and name with box with a marker for protection and identification - This is TCP / UDP encapsulation (adding a TCP / UDP header).
3. You put the box in a truck and you mark the truck with the source and destination address - This is IP encapsulation. The truck is the IP packet, and this is done by adding an IP header to the data.
4. The truck runs on the road to reach the destination address - This is the data actually travelling the physical path. Be it through the medium of physical wires, or radiowaves (wireless). The road here symbolises the physical connection between the host and the client.
Obviously, the painting example is just a comparative analogy and not totally accurate, but you get the idea. Referring to your initial comment, when you click 'Play' on your phone, you request data from RUclips, and thus you become a client. Correct. Don't think of you sending a click to RUclips server. That is not important. What is important is that you request data (video) from YT, and thus YT becomes host. And you become client. And then the whole TCP/UDP - IP cycle starts for each IP packet of data YT sends to you.
@@eighteen4379 appreciate the info
@Nada, go to POWERCERT on RUclips and watch a video of them explaining this. They make it so easy to grasp with their animation. You can use them to supplement professor's videos.
@@eighteen4379 beautiful explanation
he breaks this stuff down so insane, thanks man
As a FedEx Ground Driver, I can relate to the beginning of the Video lol
Thank You for simple explanation of TCP/UDP protocol!
7:40 See i thought that DHCP as it uses UDP has no way to verify if information has been received like TCP does. Does the external application pick up on the error and DHCP is just simply a way of resending?
Don't they just resend it..?
Hopefully someone can answer this for me. at 18:00 , UDP/5004 is used as an example for a VoIp server but I thought previously in this video he explained that ports above 1023 are Ephemeral ports that are real time ports typically from the client? so why or how is that server's port 5004?
edit : was this just an example of when he said most servers are non-ephemeral but not always? or is there more to this that I'm missing?
The ranges used for an ephemeral or non-ephemeral block of port numbers are common guidelines, but they aren't strict rules. As you've already seen, some services use whatever port number they'd like.
@@professormesser Thank You Professor!
This is my 8th time watching this video, i had to researvh a bunch of terms in there. Its a fresh morning, hopefully i understand more of it now!
Hello Professor, at the beginning I talked about that DHCP follows the UDP protocol and the UDP protocol when it sends data does not give any attention whether the data is complete or incomplete, and therefore in the minute 7:37 I spoke that DHCP is responsible for verifying and retransmitting information, can anyone explain me this?
noticed this too, im sticking with my gut and thinking he is refereing to TCP.. lots of similar acronyms and probably very easy to mix up
Probably best to trust the expert on this one. From wikipedia:
The DHCP employs a connectionless service model, using the User Datagram Protocol (UDP).
...
The DHCP ensures reliability in several ways: periodic renewal, rebinding, and failover. DHCP clients are allocated leases that last for some period of time. Clients begin to attempt to renew their leases once half the lease interval has expired. They do this by sending a unicast DHCPREQUEST message to the DHCP server that granted the original lease.
Maybe it's because I've gamed my whole life but the port 25565 is all I think about with TCP/UDP. Hosting Minecraft servers for my friends as a 12 year old really came in clutch.
I have been confused about IP Address and Ports. Watch other videos too, but this was really the best explanation, in my opinion. I can retain the information much better too.
Maybe it's his voice 😂
this one has a lot ot take in
So much! I had to pause and go absorb the entire OSI model to even make sense of this video.
Glad I did tho because I had no idea OSI was a basic framing of the entire concept of IT
Began studying literally this week. First few videos I'm like :D this is interesting, oooo I know this already, maybe getting into IT is for me! This video I'm like :O >:( :( I'm so lost lol.
How'd it go after this? did you get your cert?
Great analogical examples Professor Messur. Thank you!
WOW I learned so much on this video! Thank you! Already starting to come up with ideas for improvements
This is an amazing course and I'm loving every second of video, but I'm commenting here completely mind blown that you've used a picture of my village, Veli Losinj, as the banner for your presentation :') Small world!
This was an incredible explanation of IP
Wow...this now makes sense...thank you
Question, when explaining UDP, with no confirmation that data has made it to the other side, why does then DHCP using UDP protocol become responsible for resending the data? What did i miss
UDP is connectionless and doesn’t care about a successful connection. DHCP doesn’t support TCP/IP. DHCP sends broadcasts over UDP port 67.
Isn't the Comptia A+ for people who are new to IT. Why does this video use terms without introducing the concept of them
Just goggle some terms you need to learn from multiple sources
ITF+ would be more for people unfamiliar with technology and its terms. This, as far as I understand, are for those familiar with such things. A+ is for people who have or can use a tablet, a computer, know what a word processor is, etc. ITF+ would be for those that don’t use tech.
Also, if you have a study guide book with you, you will easily recognise those terms and it would be easier to for you to follow the video as Professor Messer is following exactly the same structure objectives.
use a computer does not automatically correlate with knowing whatever tcp is
Question: So hypothetically speaking regarding ports and applications lets say you have a server dedicated solely to FTP (I'm aware servers could contain VM's to house multiple different services) would that server only operate out of port 20 & 21?
Thanks for the update good sir 🙂
amazing explanation Proffesor
Watching for the third time because it is very useful topic😅
Hi, the amount of content in your channel is amazing. As a beginner myself I can't help feeling overwhelmed. I see so many Comptia courses in your channel. Where should I start? Thanks!
Start with A+, i already know quite abit having previously studied IT years ago but this is pretty much the place to start for newbies.
@@metalmayhem007 Thank you!
@@sakumiko9890 your welcome, I'm just starting my IT journey too, so I'm just learning A+ content to help land my first role. Good luck!
@@metalmayhem007 did you get the help desk job?
@@kingjamir2135 In fact yes! Just done ny first week. No A+ needed here in UK , to be honest they don't really hold a lot of weight here except CCNA. Net+ and sec+ can be useful just depends on company.
Really clear explanation ! Good job and thank you very much.
I definitely understand the concept. But what im hung up on is how the computer filters out all the packages. Maybe im getting ahead of myself but in a situation where there are 1000s of phones accessing a cell does the "driver of the bus" have to drive to each phone and get rejected 1000s of times before finding the right 1? And then what? Its just really fast morse code so even if the phone unlocks to receive data its just going to get random date from all the different transmissions. Only thing i can think of is its either only 1 signal is sent at a time and switches very fast or its a specific radio frequency the phone looks for that has its IP being broadcast
aaah, i tried to take the test before I had studied a while ago, and while I did pretty good I got almost none of the Networking sections because I simply didn't know what a lot of it was called or what they did. Unfortunately, that caused me to fail (which is why I'm here), but these videos are really good at explaining the exact parts that I need to study for the retake. Thanks!
did you pass after retaking?
Super informative!
Give this guy an oscar
thanks professor
My question is why ports on the sending side are randomly picked. I thought the IP address was fixed so why is the port able to change? any explanation would be helpful
Am I correct the UDP is for Voice or video calling while the TCP is like for the data that needs to be written like emails? help.
Thank you for helping so much
i have confidence in ep 1-8. im trying to rewatch and trying to fully grasp an understanding of ep9-10 and im having difficulty. Anyone have any tips? Ive rewatched ep9/10 like 4/5 times now and I cannot fully grasp the entirety of the videos.
You’re amazing man! Thanks
Thank you Professor!
why does the bedroom got direct access to the kitchen
please start showing transcript for future videos! would make note taking a lot easier :)
Transcripts for all of my videos are available on my website.
Non-ephemeral. You know nerds were involved. I love it.
Thank you for the content.
Thank you love visual metaphors
not sure if this is a dumb question but ill ask anyways. at 15:58 it says the web server and the email server is using TCP and VoIP is using UDP. My question is what types of services would you use for TCP and UDP?
Im guessing UDP is more like talking on a phone. It sends you voice and even if the other person cant hear you because of their service. Udp will just keep sending the other stuff you said after. And im assuming tcp is like a text message i guess. If you send it and it fails you can just send it again.
If i am right i hope someone can let me know. Im still learning.
TCP for integrity sensitive application data at the cost of latency. E.g. bank transactions. UDP for latency sensitive application data at the cost of integrity. E.g. mmorpg/online game data.
@@kingjamir2135 yes this is correct. the example uses VOIP for UDP because that would require some help to ensure the data is properly transferred. With VOIP, this can be like calling a friend, if they can hear you then you know the information was transferred by them replying to you.
tcp is used for stuff like modern web browsing, file transfers, emails, udp is for stuff like voIP, video calls, etc
@@HearMeLearn thanks linus! Lmao
Thank you again!
Excellent explanation
Oh my.. obj 2 is serioussss.
I thought I was confused before.
OK.....That first picture on the start is my home town Veli Losinj in Croatia....weird
Newbie here, but is it wrong to say that not "well known" port numbers are whats used for dark websites?
Excellent
is that part at 7:38 right? If the application is responsible for tracking data wouldn't DHCP NOT be responsible to retransmit????
I think you are correct. DHCP is not responsible for checking if we received, but the device that is being assigned an IP by dhcp will know when it does not get all the information. The device will tell the DHCP service that it did not get the IP addrr, and DHCP will start its sending of data again. This may sound like tcp, but in DHCP my device will not send ACK (acknowledgments) for EVERY piece of data, and will not let DHCP know that everything is good to go. DHCP sends all the data with the assumption that I will receive all the data and doesn't care further.
If you have downloaded a torrent, your are a peer receiving udp data from all active seeders that are connected to you. And when you finish the torrent and leave it running, you begin sending chunks of data to any leechers your torrent client is connected to.
I gotta learn the IP packet headers a lil more
I remember back in the day, people were making fun of a senator for saying that the internet is not a big truck.
i just drew truck in my notebook to understand
Lol
this one got intense lol
I feel like that guy in south park whom's head exploded when they were doing the Chewbacca defense
nice work
thank you
Amazing
But Ted Stevens said the Internet is not a big truck. It's a series of tubes. ;)
Me 3 min into the video: *sits up in chair*
Also me: okay we’re getting serious now😐
Great!
🍔🧇🥚🧇
XD