The segment is only in context or TCP. UDP sends datagrams.

Now I realized that before the packet left the router it has to be converted to public address and not its original private address. Thanks, clearly understood. Certainly good quality video. 😿🐴🍆🎪🎽⛏🔻

So QUIC + UDP = TCP. Ahahaha ! More seriously. This look promising. Thank you for your fast forward explanation (you don't go back to the stone edge of http protocols...Thanks God.)

Watched a BBC documentary "The Joy of Data" from 2016. It explained things amazingly.

Thanks you for this very informative video.

Hi

Watch a video about NAT Starts with the basics of ip I think we're way past that point.

10 years ago and still helps! Wow!

Will you continue making videos?

Why was this hidden?

Very lucid explanation of the concepts. Thank you.

Nice explanation, albeit much simplified. Could be more in depth. It even leaves the fact that TCP is built on top of UDP, despite that it mentions that about QUIC. Everything is built on top of UDP when you want your own internet protocol.

Thks buts; If multiple users are simultaneously in TCP/UDP server port# 42301 sessions, the only means to distinguish them is their session#s. Soooooooooooooooooo, ??????????????the single port# 42301 & multiple simultaneous session#s must be NAT translated???????????

A big thank you for this hosting wisdom! Ive experimented with GoDaddy and Hostinger, however Cloudways with TST20 couupon is the top pick.

Beter this is great

Great presentation.Explained things in a very simple but logical manner

1.25x is ideal.. But video itself is 10/10!

ok but lets say 2 computers from the same subnet send a packet to the same IP and the same port is it possible and if yes how do the router knows which pc to transfer the packet?

should they be call "segments" instead of "packages" since package is a network layer unit?

Fantastic video! Thank you for the simple explanation!

please do explain DHCP too

DAMN just watched your video from 2012 I am a first year software engineer. 10 years can change alot W you

Great video, explained really well!

10 yrs have passed and we still slowly moving to IP6 haha

I came back here because of aws natgateway . Your vid always clears doubts. Thanks for this.. Appreciate

Damn, 10 years have passed

Suggestions? Firewalls and security Groups

-DHCP server typically inbuilt in a router and a DHCP client in built in each host - When a new host is added to a network it goes through a DHCP discover process, looking for a DHCP server. Since the host doesn't know where the server is it will send a discover request (broadcasting) to all devices on the local network. Port 68 - DHCP clients, port 67 - DHCP servers - The DHCP server then responds by sending a broadcast of an allocated/offered IP addresses to all hosts. Since the server doesn't know where to find this new host it sends the DHCP offer to everyone

Please make more videos. This was hands down the best explanation for NAT Don't mind me just making myself some notes here: -There are more people available who even use more devices than there are IPv4 addresses -Local machines in a local network are all connected to a router, which is in turn connected to the internet - external public networks - To reach a public server, the packet from a local private IP has to go through the home/local router. Then through the internet - multiple routes. Then finally the webserver. - The home router changes the packet private IP source address into its own public IP address - The home router also creates a NAT forwarding table which helps with return packets to know which packets go to which host in the local network by mapping host's private addresses to reserved public addresses in it - The web server creates a response packet with it's destination as a the home router which is a public IP - At the home router the packet's destination IP address is changed to the corresponding/matching local private IP address on the NAT forwarding table. Then the packet will be forwarded to the local host

Gosh this was understandable. Noone can't even try to explain things that easily and consisitently.

You really explained glue records as simply as possible. Thanks.

That's crisp and clear..

go ahead and adjust playback speed to 1.5...you're welcome

Thankssss!

6:51 I do not understand how QUIC can be slower than TCP in term of bandwith.

This video (with the tidbits about glue records, what would happen without hardcoded zone records, etc) was so much more informative and well done than every other DNS video that spend 10 minutes with graphics to say absolutely nothing more than vaguely, "it's a hierarchy".

I see what you did with FLOUDCLARE

I had no idea it was so chilly in san antonio