Every network engineer at some point will need to explain the difference between TCP and UDP, along with a few details about the protocol. Whether for a certification exam like the CCNA or Network+, or for a job interview. Let's keep it simple. In this video we will chat about the differences between TCP and UDP using this pcap example in Wireshark: Download and follow along - www.cloudshark.org/captures/af9dc6ba427a
Hi Chris, I always enjoy your video. I sometimes have to explain about this two transport protocol to my students, cause I am a lecturer. My favourite way to explain this 2 protocol is to compare TCP with a phone call, and UDP with a mail delivery. A phone call can only be proceed if both parties agree for a conversation, that's implemented by dialing AND pick up the phone... So that's exactly the handshake in telephone system. Meanwhile, we can always send email and don't need to worry the state of the recipient. That's the point that mail delivery and UDP don't need initial or handshake process.
I'm studying for my CCNA. At the moment I'm learning about TCP vs UDP. So your video is very helpful. Those practical demonstrations are awesome. They help me to understand things better. Thanks man.
Finally! explained simply and straight forward, and the wireshark capture is definitely an important bonus. Thank you so much! we need a similar video explaining IPsec protocol IKE and ESP please! and if the packet capture can be included even better. Until the next one!
Quite a good summary about the main differences between TCP and UDP ... but one difference (which at least I find also important) was entirely missed: A tcp-connection (being a connection) is between two distinct endpoints. So, if your program talks to 10000 clients at the same time, it needs to maintain 10000 connections and will therefore need 10000 socket-filedescriptors. A UDP-socket on the other side (being connectionless) can talk to 10000 clients at the same time just using the one socket-filedescriptor. The one udp socket-fd can be used to receive packets from all remote peers and also send packets to them.
Hi Chris, i just read book related tcp/ip and found this statement "One difference between TCP and UDP is that UDP preserves message boundaries." what is "message boundaries" means?
Hey Nanda! great question. So when an application sends data to the kernel for transmission, it can do so in "chunks" of data. The start and end of those chunks of data are called "message boundaries". TCP does not care where data starts and ends because it is a stream-based protocol. So it chops data up and sends it along, regardless if it is at the middle or end of the boundary. (Hint - you can usually tell the end of the boundary by the PSH bit) UDP however will preserve the boundaries it is given by the application. So if 800 bytes is handed down, a UDP packet of 800 bytes will go out, without waiting for more data to fill the packet, etc. Hope this helps answer the question!
@@masaksehat24 If the application uses a small block size, TCP can kick it out with a PSH bit set. But since TCP is designed as a stream-based protocol, it not supposed to look for message boundaries.
Hey Chris just found you on Dave’s channel I like the way you present. Do you have a beginners course for wire shark? I have a small experience with it in class but my class was a boot camp so not much time was spent on it. Please if you have a course that I can buy please let me know.
Hey Daniel! Thanks for stopping by the channel and for the comment. Yes, I do have courses you can take to get up to speed on Wireshark - one is on-demand on Pluralsight - www.bit.ly/wiresharkintro The other is a live, instructor-led (me) course that I teach via zoom www.bit.ly/virtualwireshark I hope these help you on your journey!
You say "Ethernet" is layer two. Can you describe in more detail why Ethernet is considered layer 2 to someone running an Ethernet cable who may consider "Ethernet" (the cable) as layer 1? The cable is layer 1, but the layer 2 encapsulation of frames transmitting through the Ethernet cable is known as "Ethernet"? Confusing
I am kinda very upset that why doesn't my university teachers mention about wireshark at all and why this topics arn't shown with wireshark in action during lectures. Till date whenever someone mentioned UDP, i visualized bytes flowing in air and whenever someone mentioned TCP, i could see a wire between 2 points and thats it i understood. Damn what a waste of my time during the degree .. Thanks Anyway Chris !!!!
Every network engineer at some point will need to explain the difference between TCP and UDP, along with a few details about the protocol. Whether for a certification exam like the CCNA or Network+, or for a job interview.
Let's keep it simple.
In this video we will chat about the differences between TCP and UDP using this pcap example in Wireshark:
Download and follow along - www.cloudshark.org/captures/af9dc6ba427a
Hi Chris, I always enjoy your video. I sometimes have to explain about this two transport protocol to my students, cause I am a lecturer.
My favourite way to explain this 2 protocol is to compare TCP with a phone call, and UDP with a mail delivery. A phone call can only be proceed if both parties agree for a conversation, that's implemented by dialing AND pick up the phone... So that's exactly the handshake in telephone system. Meanwhile, we can always send email and don't need to worry the state of the recipient. That's the point that mail delivery and UDP don't need initial or handshake process.
Thanks for the comment! That is a great analogy.
studying for the CompTIA Network plus exam that actually a really good explanation that helped me understand a lot better thank you
I'm studying for my CCNA. At the moment I'm learning about TCP vs UDP. So your video is very helpful. Those practical demonstrations are awesome. They help me to understand things better. Thanks man.
Dude. You're so helpful and using wireshark to give examples is 🔥🔥
Glad you think so!
awesome work...it was straight forward and made sense. Thank you for doing this.
You are a very good teacher. Thank you for the videos.
Glad you like them! Thank you very much for the feedback!
really good video, thank you for the simple explanations and practical examples in wireshark!
Thanks for the comment Angelo!
Finally! explained simply and straight forward, and the wireshark capture is definitely an important bonus. Thank you so much! we need a similar video explaining IPsec protocol IKE and ESP please! and if the packet capture can be included even better. Until the next one!
Glad it helps Jair! And thank you for the suggested videos as well. I'll see if I can add them to my list.
@Chris Greer I agree, and how about this for even MORE fun, UDP across an IPsec tunnel and trying to troubleshoot dropped packets.
Thanks for your time and dedication in doing this content, man! Clear and nicely presented!
Thanks for the comment David!
Hey Chris, super video. Easy breakdown and simple to understand. Thank you👍.
Great explanation especially with the Wireshark example
Superb...a big fan of ur videos.
Thanks for the comment and for stopping by the channel!
No words to explain😍 Best thing is we are getting this valuable information for free of cost.
Glad it helps you! Please share with anyone you think could benefit, like, and sub!
Awesome! 10/10 friend. Keep up the good work.
Thank you so much. I will check every video on TCP playlist on your channel. Your explanations are simple and can be grasped easily. Kudos Chris
Thanks!!
good video :) had to watch this for HW
Glad you enjoyed it!
Man your videos are always help full 👍👍 keep going 👍
Thanks, will do!
Dude you’re awesome. Thanks so much for these vids
excellent explanation! Thanks, my dude :)
Glad you liked it!
Quite a good summary about the main differences between TCP and UDP ...
but one difference (which at least I find also important) was entirely missed:
A tcp-connection (being a connection) is between two distinct endpoints.
So, if your program talks to 10000 clients at the same time, it needs to maintain
10000 connections and will therefore need 10000 socket-filedescriptors.
A UDP-socket on the other side (being connectionless) can talk to 10000 clients
at the same time just using the one socket-filedescriptor. The one udp socket-fd
can be used to receive packets from all remote peers and also send packets to them.
From morroco 🇲🇦you are the best man
Thanks!
your expression way is amazing.
Thank you!
Wow master is back...
Glad you like the channel!
Awesome lesson! tyvm
Awesome video. I’m stealing this…
Go for it! Yours for the stealing... Just please promote my channel when you do. Thanks!
Wow this was explained very clearly 👌🏾
Great Explanation! Thank you.
Glad it was helpful!
You're the best!
Am glad I came across to know the difference.
By the way, which firewall uses UDP?
Thanks.
Your videos are just catalyst for me to get back and focus on Packet analysis 🙄, thanks.
Awesome! keep on digging.
Great video. Thank you.
very good comprehension video
Glad you think so!
Thanks, Chris
Best explanations
Nice video my brother
Thanks Tristan! Great to see ya!
Hi Chris, how to measure packet loss, jitter, throughput of UDP using wireshark ?
Great question - I will look at covering it in a future video.
@@ChrisGreer thanks Chris..
Hi Chris, i just read book related tcp/ip and found this statement "One difference between TCP and UDP is that UDP preserves message boundaries."
what is "message boundaries" means?
Hey Nanda! great question. So when an application sends data to the kernel for transmission, it can do so in "chunks" of data. The start and end of those chunks of data are called "message boundaries". TCP does not care where data starts and ends because it is a stream-based protocol. So it chops data up and sends it along, regardless if it is at the middle or end of the boundary. (Hint - you can usually tell the end of the boundary by the PSH bit) UDP however will preserve the boundaries it is given by the application. So if 800 bytes is handed down, a UDP packet of 800 bytes will go out, without waiting for more data to fill the packet, etc. Hope this helps answer the question!
@@ChrisGreer so, tcp can not do that?
@@masaksehat24 If the application uses a small block size, TCP can kick it out with a PSH bit set. But since TCP is designed as a stream-based protocol, it not supposed to look for message boundaries.
@@ChrisGreer well noted. thank you Chris
Hey Chris just found you on Dave’s channel I like the way you present. Do you have a beginners course for wire shark? I have a small experience with it in class but my class was a boot camp so not much time was spent on it. Please if you have a course that I can buy please let me know.
Hey Daniel! Thanks for stopping by the channel and for the comment. Yes, I do have courses you can take to get up to speed on Wireshark - one is on-demand on Pluralsight - www.bit.ly/wiresharkintro The other is a live, instructor-led (me) course that I teach via zoom www.bit.ly/virtualwireshark I hope these help you on your journey!
Why do they call tcp/ip but not udp/ip. Does udp packet have ip address?
Hi Chris. How can I get your packet head t-shirt :)
packetpioneer.creator-spring.com/ check it out on my store! Or you can find links to it from my channel under the "Store" view.
You say "Ethernet" is layer two. Can you describe in more detail why Ethernet is considered layer 2 to someone running an Ethernet cable who may consider "Ethernet" (the cable) as layer 1?
The cable is layer 1, but the layer 2 encapsulation of frames transmitting through the Ethernet cable is known as "Ethernet"?
Confusing
hello chris
I am kinda very upset that why doesn't my university teachers mention about wireshark at all and why this topics arn't shown with wireshark in action during lectures. Till date whenever someone mentioned UDP, i visualized bytes flowing in air and whenever someone mentioned TCP, i could see a wire between 2 points and thats it i understood. Damn what a waste of my time during the degree ..
Thanks Anyway Chris !!!!
Glad you stopped by the channel Test Shar! Feel free to share the video with anyone you think would benefit. Thank you
Let me tell you a UDP Joke, but i'm afraid you won't get it.
Thompson Amy Allen Brian Hernandez Deborah
Jackson Timothy Anderson Scott Walker Mary
I have a good UDP joke.
I don't care if you get it.
ACK! Oh wait... wrong protocol. 🙃 Gotta love TCP humor.
I have joke on UDP.
But you won't get it.
Haha! Gotta love that one