A: I want to talk to you B: I acknowledge that you want to talk to me, I also want to talk to you A: I acknowledge that you want to talk to me A: The weather today is nice B: Indeed B: The wind makes me want to go for a walk A: Indeed A: I need to go now B: I acknowledge that you need to go B: I need to go now A: I acknowledge that you need to go
It's like listening to awkwardly polite people ending a phone call... "Well, I gotta run." "Yup, I hear ya. Didn't mean to keep you so long." "No, you're good man. It was nice talking to you." "Yeah it was. Tell the wife I say hello." "Roger that. I'll pass on the the message. Stay safe!" "Gotcha. You too." "You too." "Later." "Bye."
TCP connections are like marriage counseling exercises. "I affirm and acknowledge your feelings." "I acknowledge your acknowledgement of my feelings." "I acknowledge that you acknowledge my acknowledgement."
Gotta say, I've learned more from this 13 part series in one night than I could have in weeks of looking up information elsewhere. The information was presented in such a clear and concise way, with very easy to understand explanations. Absolutely fantastic work!
Great series. Any plans for follo up for UDP and explaining how DNSs work? There are times you refer to the TCP unit as a byte but really it is a segment. Also you forgot to mention window sizes.
First of all, thank you for this fantastic series. It is really well-put. One minor nit about this video specifically: when choosing the initial SEQ numbers in handshake, while it makes sense to set them to some small readable value, it would probably make more sense to make them different to avoid possible confusion/magic number syndrome. Say, client's SEQ = 0, server's SEQ = 100.
I simply LOVE when you show the practical usage of the theory you made. And the practical usage is the same of the theory you used, I mean, the IP's, seq numbers, all matching up, makes it waaaay easier to understand.
I have a textbook, an instructor's lecture and office hours, his slides, and it just didn't click until I saw this. Your excellent explanation saved me a lot of time and energy. Thanks a bunch.
No. It should be Seq number 24 because client is expecting last packet with the sequence number 24 thats why it sent ack number 24 to the server otherwise it will consider as the packet is lost somewhere.
I feel compelled to let you know sir that I have been studying c.s. for a while now. You are by far the best person I have found yet that can explain things (not just in this particular video) in such a way that I feel I can thouroughly understand. I would like to sincerely like to thank you very much for taking the time to produce so much content , that in my eyes is valuable as gold, and FREELY share it. THANK YOU, please continue to make more content. I would be particularly interested in your take on 2020 /19 networking concepts as we all know our connection are be listened to, I would love to hear you perspective.
The philosophies of ben eater reveal themselves in the writings... “Wireshark is nice because,” “Wireshark is nice enough to,” “Does this really nice thing.” He is trying to tell us of the importance of gratitude for a healthy mind. Congratulations, you’ve created scripture.
Hey Ben, I am currently a college undergrad, with no job and terrible GPA, I lost all my interest in studies because of the terrible teachers I had and ofcourse my attitude of not feeling motivated towards anything. These 13 Videos made me think of how beautiful things can really be, finally starting to get back to the right track. Better fail then never try.. Thanks Man!
Every single scamming video that i watch or called me were INDIAN i am not trying to be racist here but seriously what’s up with these people ? don’t they have dignity ? you can literally search IRS scams and every single one of them are INDIAN, wtf is wrong with these people ?
Wow. What a great bunch of videos! I always thought this stuff was extremely difficult to grasp but the way you broke it down made it really clear. Thanks!
I'm a teacher of Computer Networking in Colombia and I've been seeing your networking tutorial. Let me you say that all of these videos are amazing, absolutely clear and well explained. So I wanna use those for my e-learning classes but not all of my students are bilingual, so I'd like to ask your permission for publish the translation in Spanish of these tutorial.
I don't know what it is about Ben's way of explaining things, but I just get it no matter how complicated the thing is. I tried learning this stuff before and it was daunting and hard. But I just binged this entire thing in one go and I understand the basics of networking now. Thanks Ben!
This has been the first large scale networking explanation that has actually made *clear* sense to me; most that I've seen explain a few aspects well but leave confusion when bringing it all together. Thank you so much for making this videos!
I know this video is old etc, but would anyone able to explain why the SEQ number is 1 during the FIN bit process and not 2? It seems strange that the host in this particular instance sends two SEQ bits, both with the value of 1.
woah cool!! one of the best networking tutorials that i have watched.. anybody who is thinking whether to watch it or not to understand Networking, please do.. Thank you Ben. please upload tutorials on some of the uncovered topics as well.
Those videos help me answer forgotten question when i was a child, like how computers can communicate so fast? I never thought that would be so interesting learn about it. Fascinated and glad for that material, thank you!!!!
@@uzdik.student AFAIK... If the client does not receive an ACK, it indicates a packet loss. The packet has a sequence. Therefore, it easy to know whether there packet loss. One more thing: The TCP Flag that initiates a connection is SYN, not ACK.
Well, I have to say, for a lazy person like me, it's amazing how I watched the entire playlist at one stretch even though I know nothing of computer science. Thank You for this. I was completely confused as to where to start. This gave me a pretty good view.
This is really really really helped me a lot...!! Thanks a bunchh for your great explanation I'm really grateful to find a Internet Protocol tutorial, which is really hard to find... Please continue making videos to help those who really wants to learn.
I've completed your playlist sir, How much.....How much......easier the lessons are! you've made it sir. Can you please and please produce more videos on NETWORKING? I've learned a lot, really a lot sir. How can I give more thanks to you!!!!!!!!!!!
@Ben Eater Why 192.168.192.10 is sending FIN-ACK to 192.168.0.147 instead of sending FIN first then followed by ACK from client and again client sends FIN and server sends ACk back to client.
Just wanted to point out, that TCP (usually) doesn't work as "send packet, receive ack, send packet, receive ack", but more likely "send a bunch of packets, wait for ack". First case is simply too ineffective (in terms of a bandwidth).
Dear Sir, I have watched almost every of your videos. I kindly request you to build a series on internet connection on the custom hardware like the 8 bit computer or the 6502 computer. I am currently building a 32 bit computer with vga output and a usb keyboard, mouse input. I am also planing to build an OS for it. From your kind subscriber. Thank you for your kind support.
why is it that connection end-points are addressing each other using 192.168.x.x addresses, but my public IP address starts with something completely different? don't incoming packets to me get addressed to my public IP address and not the one i use to identify my device on my LAN?
I struggle to understand the server IP... If I remember well « 192.x.x.x » is C class address so the default mask is 255.255.255.0, it would mean that the client and the server aren’t on the same network which is totally possible but weird as C class addresses are mainly if not exclusively used for local networks (as they provide only 256 addresses). They could be local addresses but Wireshark shows tcp requests, and they use public IPs, not private ones (as the rooter on the server side has a static rule to forward requests to the server application through it’s private IP and on the client side, the rooter creates the forwarding rule at the connection). Please tell me where I am wrong !
Interesting that a lot of this stuff seems particularly arbitrary. Each piece of course exists to solve specific issues, however the solutions used are neither the simplest possible solution, nor the most efficient solution. TCP/IP seems to have won the internet due to a combination of being "good enough" to work for most applications, and maybe being picked by the right big players (companies & universities?) at the time.
I really love the content you make, but could you maybe more mindful with your spectator's eyes when transitioning from a completely black screen to a completely white screen. It literally makes my head hurt A LOT! But thanks for the great content, I really appreciate it!
I may be wrong but I believe the client won’t be able to speak to the server since they are trying to communicating on different ports. Example ssh (port 22): doesn’t the client have to send out on port22 for the server to receive on port 22? Someone please correct me if I’m wrong.
How did you interrogate the network routers (i.e. to obtain their routing tables)? I already knew quite a bit of this, but you taught me many details and straightened out a few false assumptions. I would also be interested in ISP gateway router setup for home or office.
"normally it starts with a random number, but in this case to make things simpler i'm gonna start with 0" 0 is not a random number? 0 is just as random as any other number!!!
I saw networking playlist but in pc we set our ip ourself to eg 192.168.1.2 and whom which are trying to connect maybe set his ip to that, and for online games eg we should do portforwarding how that works?
@sender and receivers maintain separate syn and ack numbers.. In the last example client sends fin bit with sequence #2 as it already sent sequence #1 in the handshake
2:15 actually the protocol says that it takes whatever the seq # is and add 1 to it , that is the reason ack is set to 1 and not just any other number.
server: i want to end this conversation client: i acknowledge that you want to end this conversation client: since i have acknowledged that you want to end this conversation, i also want to end it server: i acknowledge that you also want to end this conversation
A: I want to talk to you
B: I acknowledge that you want to talk to me, I also want to talk to you
A: I acknowledge that you want to talk to me
A: The weather today is nice
B: Indeed
B: The wind makes me want to go for a walk
A: Indeed
A: I need to go now
B: I acknowledge that you need to go
B: I need to go now
A: I acknowledge that you need to go
A: Have you heard of the high elves?
B: Nothing I'd like to talk about.
My family is not gonna be happy when they hear the new rules.
Wow, it's helped me to more easily understand the TCP Connection, thx bro.
I watched end to end in one go and I learned more about the data transmission than during a whole semester in uni. Awesome series!
WOW. That's binge-watching :c) I've just finished the whole thing as well - but it took me much longer than it took you :c)
That means you weren't trying hard enough.
@@nollix lmao nah fr
No kidding!!
@@nollixnah
Ben?! Why dont you keep doing these tutorials? There are lot to cover yet((
Building an 8-bit computer networking hardware..
@@okgfwij That took a while
I am sad that the playlist is over :(
This is awesome :) I wish you do more this kind of videos, about HTTP/HTTPS, DNS, DHCP and IPv6 :)
It's like listening to awkwardly polite people ending a phone call...
"Well, I gotta run."
"Yup, I hear ya. Didn't mean to keep you so long."
"No, you're good man. It was nice talking to you."
"Yeah it was. Tell the wife I say hello."
"Roger that. I'll pass on the the message. Stay safe!"
"Gotcha. You too."
"You too."
"Later."
"Bye."
LOL, your comment just makes it even easier to remember these procedures
Really great playlist, learnt a lot, these are exact the tutorials I was searching.
TCP connections are like marriage counseling exercises. "I affirm and acknowledge your feelings." "I acknowledge your acknowledgement of my feelings." "I acknowledge that you acknowledge my acknowledgement."
Gotta say, I've learned more from this 13 part series in one night than I could have in weeks of looking up information elsewhere. The information was presented in such a clear and concise way, with very easy to understand explanations. Absolutely fantastic work!
Great series. Any plans for follo up for UDP and explaining how DNSs work? There are times you refer to the TCP unit as a byte but really it is a segment. Also you forgot to mention window sizes.
First of all, thank you for this fantastic series. It is really well-put.
One minor nit about this video specifically: when choosing the initial SEQ numbers in handshake, while it makes sense to set them to some small readable value, it would probably make more sense to make them different to avoid possible confusion/magic number syndrome. Say, client's SEQ = 0, server's SEQ = 100.
True, it made things confusing, better to use different initial SEQ numbers for client and server.
I think he chose those values so that Wireshark will match up with the numbers
I simply LOVE when you show the practical usage of the theory you made. And the practical usage is the same of the theory you used, I mean, the IP's, seq numbers, all matching up, makes it waaaay easier to understand.
Thank you for this amazing lecture.
Shouldn't the last ACK packet from server to client be with seq #24 and ack #2 ? Correct me if I am wrong. Thanks.
It is same in packet capture. He actually means acknowledgment 2 but wrote sequence number 2 in lecture.
Please talk about , nat , ssh , tunneling , http(.9,1,1.2,2,quic), udp, .. and thanks for this greate play list
I have a textbook, an instructor's lecture and office hours, his slides, and it just didn't click until I saw this. Your excellent explanation saved me a lot of time and energy. Thanks a bunch.
Your name is Cisco?? :D
Or you're just into networking too much?
Shouldn't that last 'seq 2' be 'ack 2'? Because it is an ACK, an the server expects the next seq to be 2...
+Mike Voets
Yes it should be
No. It should be Seq number 24 because client is expecting last packet with the sequence number 24 thats why it sent ack number 24 to the server otherwise it will consider as the packet is lost somewhere.
Um yeah it is. Look at Wireshark's representation from 07:00 onwards, if you look at the last entry there's an ack with a value of 2.
Yes, that is true! It should be corrected to prevent confusion.
Yes, it is seq 24, and ACK 2.
excuseme Ben but the last server seq number is 24 (what the server expects) and the last ack number is 2 (client seq + 1)
Is it right?
Nicolò yeah, I also think you are right.
"Seq: 24, Ack : 2" from server to client
You are right, you can confirm your suspicion with wire shark at the end
I've watched all 13 videos!! Amazing work you've done here!!! Thank you so much for these lectures!!! You are a fantastic professor!!
I feel compelled to let you know sir that I have been studying c.s. for a while now. You are by far the best person I have found yet that can explain things (not just in this particular video) in such a way that I feel I can thouroughly understand. I would like to sincerely like to thank you very much for taking the time to produce so much content , that in my eyes is valuable as gold, and FREELY share it.
THANK YOU, please continue to make more content. I would be particularly interested in your take on 2020 /19 networking concepts as we all know our connection are be listened to, I would love to hear you perspective.
The philosophies of ben eater reveal themselves in the writings... “Wireshark is nice because,” “Wireshark is nice enough to,” “Does this really nice thing.” He is trying to tell us of the importance of gratitude for a healthy mind. Congratulations, you’ve created scripture.
So that 3 way handhsake is basically:
"Hi do you hear me?"
"Loud and clear, do you hear me though?"
"Yup"
And now we know we both hear each other.
Such a cool series. Thanks so much! It's incredible how much data is being sent and decoded all over the world....
Hey Ben, I am currently a college undergrad, with no job and terrible GPA, I lost all my interest in studies because of the terrible teachers I had and ofcourse my attitude of not feeling motivated towards anything. These 13 Videos made me think of how beautiful things can really be, finally starting to get back to the right track.
Better fail then never try..
Thanks Man!
It's been 4 years, have you improved? :)
I'm so grateful to you :) These videos on networking helped me learn alot :) I rarely comment but you deserve it :) Great Job!
😑
Every single scamming video that i watch or called me were INDIAN
i am not trying to be racist here but seriously what’s up with these people ? don’t they have dignity ?
you can literally search IRS scams and every single one of them are INDIAN, wtf is wrong with these people ?
Wow. What a great bunch of videos! I always thought this stuff was extremely difficult to grasp but the way you broke it down made it really clear. Thanks!
I'm a teacher of Computer Networking in Colombia and I've been seeing your networking tutorial. Let me you say that all of these videos are amazing, absolutely clear and well explained. So I wanna use those for my e-learning classes but not all of my students are bilingual, so I'd like to ask your permission for publish the translation in Spanish of these tutorial.
This video is wrong, though.
Taxtro Don't just make a trite comment like that and then take off, explain precisely and exactly what you mean.
Best instruction I have found on this. Excellent video
I don't know what it is about Ben's way of explaining things, but I just get it no matter how complicated the thing is.
I tried learning this stuff before and it was daunting and hard. But I just binged this entire thing in one go and I understand the basics of networking now.
Thanks Ben!
This has been the first large scale networking explanation that has actually made *clear* sense to me; most that I've seen explain a few aspects well but leave confusion when bringing it all together. Thank you so much for making this videos!
Thank you so much, you helped me a lot. I really liked the idea of showing the TCP header
I know this video is old etc, but would anyone able to explain why the SEQ number is 1 during the FIN bit process and not 2?
It seems strange that the host in this particular instance sends two SEQ bits, both with the value of 1.
I dont think that ACK counts toward the sequence number
This series is fantastic! It covered everything in exactly the detail I was hoping for. Thank you so much, Ben!
This series is one of the best things I've seen on the internet in a long while
woah cool!!
one of the best networking tutorials that i have watched..
anybody who is thinking whether to watch it or not to understand Networking, please do..
Thank you Ben. please upload tutorials on some of the uncovered topics as well.
hey Ben , don't you have plan on keeping this series going ? very well explained i wish there were more of these...
Thanks for the tutorial. PLEASE do another.
AOMis
Videos published 9 years ago, and relevant to this day. Awesome series!
Those videos help me answer forgotten question when i was a child, like how computers can communicate so fast? I never thought that would be so interesting learn about it. Fascinated and glad for that material, thank you!!!!
When the second ACK is sent (to the server), how does the client know it was received by the server? Who "establishes" the connection at that point?
@@uzdik.student AFAIK... If the client does not receive an ACK, it indicates a packet loss.
The packet has a sequence. Therefore, it easy to know whether there packet loss.
One more thing: The TCP Flag that initiates a connection is SYN, not ACK.
Well, I have to say, for a lazy person like me, it's amazing how I watched the entire playlist at one stretch even though I know nothing of computer science. Thank You for this. I was completely confused as to where to start. This gave me a pretty good view.
This is really really really helped me a lot...!!
Thanks a bunchh for your great explanation
I'm really grateful to find a Internet Protocol tutorial, which is really hard to find...
Please continue making videos to help those who really wants to learn.
Thank you for this great playlist! Keep up the good work!
Amazing play list! GG
I've completed your playlist sir, How much.....How much......easier the lessons are! you've made it sir.
Can you please and please produce more videos on NETWORKING?
I've learned a lot, really a lot sir. How can I give more thanks to you!!!!!!!!!!!
@Ben Eater Why 192.168.192.10 is sending FIN-ACK to 192.168.0.147 instead of sending FIN first then followed by ACK from client and again client sends FIN and server sends ACk back to client.
Does the Client send Seq Number 1, in ACK for Establishment?
If I am correct, is the FIN bit suppose to send Seq Number 2?
Thank you! Excellent tutorial!
I have a question about Tcp receive window size
i have this example from Wireshark :
client A :syn, win=8192 , ws=4 ====>
my wireshark capture doesn't have a separate fin/ack for each side, just one FIN,ACK from client and a final ACK from server
I have been following your videos, and they are really a great learning sources. Thanks a log
Just wanted to point out, that TCP (usually) doesn't work as "send packet, receive ack, send packet, receive ack", but more likely "send a bunch of packets, wait for ack". First case is simply too ineffective (in terms of a bandwidth).
Dear Sir, I have watched almost every of your videos. I kindly request you to build a series on internet connection on the custom hardware like the 8 bit computer or the 6502 computer. I am currently building a 32 bit computer with vga output and a usb keyboard, mouse input. I am also planing to build an OS for it. From your kind subscriber. Thank you for your kind support.
Great serie about Networkin!!! Thanks for shared your knowledges. You are an amazing communicator and teacher.
why is it that connection end-points are addressing each other using 192.168.x.x addresses, but my public IP address starts with something completely different? don't incoming packets to me get addressed to my public IP address and not the one i use to identify my device on my LAN?
Hi, great explanation of TCP. At 6:45 should the last ack from server side be ack 2 instead of seq 2?
I struggle to understand the server IP... If I remember well « 192.x.x.x » is C class address so the default mask is 255.255.255.0, it would mean that the client and the server aren’t on the same network which is totally possible but weird as C class addresses are mainly if not exclusively used for local networks (as they provide only 256 addresses). They could be local addresses but Wireshark shows tcp requests, and they use public IPs, not private ones (as the rooter on the server side has a static rule to forward requests to the server application through it’s private IP and on the client side, the rooter creates the forwarding rule at the connection). Please tell me where I am wrong !
-Oh, dear.
-What is it?
-I've spontaneously combusted.
Thomas Gary Gonzalez Donald Lewis Betty
Interesting that a lot of this stuff seems particularly arbitrary. Each piece of course exists to solve specific issues, however the solutions used are neither the simplest possible solution, nor the most efficient solution. TCP/IP seems to have won the internet due to a combination of being "good enough" to work for most applications, and maybe being picked by the right big players (companies & universities?) at the time.
Rodriguez Anna Lopez Brenda Taylor Dorothy
Correction: At 6:46 last ACK after FIN would be SeqNum 24 and AckNum 2
Why should the Acknoledgement Number be increased by number of bytes within the last package?
I really love the content you make, but could you maybe more mindful with your spectator's eyes when transitioning from a completely black screen to a completely white screen. It literally makes my head hurt A LOT! But thanks for the great content, I really appreciate it!
Taylor Jason Martin Elizabeth Jackson Timothy
I would feel guilty if i don't leave a thank you note for this awesome series!!!!!!! Thank you Ben.
I may be wrong but I believe the client won’t be able to speak to the server since they are trying to communicating on different ports. Example ssh (port 22): doesn’t the client have to send out on port22 for the server to receive on port 22? Someone please correct me if I’m wrong.
Please keep these things going, please!!
I just looked at the thumbnail and clicked asap, purely awesome
Jones Steven Rodriguez Betty Martinez Daniel
How did you interrogate the network routers (i.e. to obtain their routing tables)? I already knew quite a bit of this, but you taught me many details and straightened out a few false assumptions. I would also be interested in ISP gateway router setup for home or office.
Ur series are awesome.
Upload something of Networking related to prerequisite for ethical hac***g
Thanks Ben. Please explain control-flow. how does a slow link will stop client from sending too many data. thank you
I believe that the very last packet from the server should have Ack=2 instead of Seq=2 @6:48
So many gems in this series. Thank you Ben!
Nice, but you should use different numbers for the sequence # and the ack #. A bit confusing to follow.
Johnson Elizabeth White Dorothy Jones David
@ben the receiver only ack on how much byte it received, first example ack to 22, not 23.
"normally it starts with a random number, but in this case to make things simpler i'm gonna start with 0"
0 is not a random number?
0 is just as random as any other number!!!
I saw networking playlist but in pc we set our ip ourself to eg 192.168.1.2 and whom which are trying to connect maybe set his ip to that, and for online games eg we should do portforwarding how that works?
Miller Steven Young Steven Young Richard
thank you so much for this concise highly informative Video ❤️
Lopez Kenneth Jackson Mary Martinez George
Very very good!!
I would love to see more of this playlist!
Video description: Want to see more? Leave a comment!
My comment: DNS
@sender and receivers maintain separate syn and ack numbers.. In the last example client sends fin bit with sequence #2 as it already sent sequence #1 in the handshake
Garcia Donald Garcia Frank Thomas Anthony
Miller Margaret Williams Cynthia Martinez Ronald
Why does the ACK number increment by 1 when establishing a connection when there is no data sent?
That was my thought, do you know the answer?
Rodriguez Patricia Williams Amy Garcia William
in the last step, the server should send ack #=2 instead of seg #=2 right?
Worst part is even with the material of such quality i have to go trough it 10 times minimum to wrap my head around it
Can't imagine a video from 9 years ago is still super useful
In the tcp diagram there is a Window segment, what is this Window segment for?
Johnson Nancy Hernandez Sarah Anderson Scott
i think the example of seq number and ack number is confusing
Thanks...I don't get it. But I will one day!
2:15 actually the protocol says that it takes whatever the seq # is and add 1 to it , that is the reason ack is set to 1 and not just any other number.
server: i want to end this conversation
client: i acknowledge that you want to end this conversation
client: since i have acknowledged that you want to end this conversation, i also want to end it
server: i acknowledge that you also want to end this conversation
Such an informative playlist