Less related to networking, but another video idea in this style might be explaining the difference between Encoding, Encryption, Hashing etc. Those terms get misused a lot and are really useful to understand
Please please please can you make a video about application layer or more specifically DNS and its hierarchy and types? Or routing explanation in a nonconfusing way? Sorry if I asked maybe something unrelated to what you wanted to do
Been watching your content for a couple years now and I am absolutely floored with the change in quality and presentation you've made over time. I am excited to see what you create in the future. I have been a big fan of your Minecraft stuff, it used to be a big part of my life way back in the alpha days when a friend and I used to run a server. Edit: The advertisement at the end was awesome!
@2:04 you made a cardinal mistake. Its not called a switch, its called a router, The IP Layer is layer 3 and the Physical Layer is Layer 1 and a Switch is a layer 2 device. You forgot? Oh you told it at 3:20 but its super important... Sorry
Nice one but in my opinion hiding the ethernet layer is a bit of an over simplification :/ In a real network without this concept you cannot understand the differences between switches and routers and the concept of routing is what people get more and more confused. Good if it's a part 1 video. But not enough if you wanted it to be a deep dive
I assume it is meant to be a part 1 video, kind of like I was making the same video pt 1 on my other channel (not going to advertise) but called it TCP for dummies. Otherwise it’s indeed the most basic info we learn in school. Very clean and pleasing though.
@@OwO-. newbie here too. This vid was brilliant from my perspective--I see the terminology all the time, but haven't taken the time to define them. OP's comment makes me wonder about LiveOverflow's audience makeup. Btw, LO's CV is unquestionable and on display, so there's no doubt in him. Regardless, I appreciate him making videos like this, reaching down to a pleb like me to bring me up to speed.
Same! I trested OSI layers as blackboxes, as mentioned in the video, but could never find a wall-breaking introduction that would make sense. All the diagrams I've seen are much clearer after this vid. I understand some people may find this offensively easy, but that wasn't the case for me and I really appreciate LO effort here
I can see why you did it, but even implying for simplicity that switches look at IP addresses is definitely going to make any network admin cringe. However, the main point of the video is that most hackers don't need to know how their packets are transmitted and just need to know general information about how the protocol works. Since accepting abstraction as a hacker (most the time) appears to be the main thesis of this video, this video works. Networking can be a very dry topic. Networking 1 was the only class I've ever taken where the professor had to give us a 5 minute break in the middle so we didn't fall asleep. And that was only the first 3 of ~16 total credit hours worth of classes I needed on networking for my undergrad. So tl;dr: This video is for hackers who don't know anything about networking. It is a deep dive, but networking is so deep a subject that this barely scratches the surface.
You can think of it like taking a letter and wrapping it in envelopes, with each envelope containing addressing information. First it gets wrapped in a TCP or UDP envelope, then that gets wrapped in an IP envelope, then THAT gets wrapped in an Ethernet or WiFi envelope, and then that gets passed to your mail courier.
i would’ve like to have seen layers 4-7 covered, although in fairness that likely could’ve been it’s own video. i run a web server with multiple dns records pointing to the same server and am admittedly confused how it determines which subdomain is which for the server
Exactly, if you are a hacker, learn and ask questions yourself how it works. If you understand the basics very well of the OSI and TCP/IP layers then everything will makes sense to you. Networking is an art. In reality, you can write code to interact to your TCP/IP driver in Windows using Windows Sockets API, that interacts with Network Driver Interface Specification (NDIS) , that interacts with your NIC driver. So many abstractions ;) Do not forget, there are more protocols then TCP/IP, before we had IPX/SPX. Novell used NetBEUI and Microsoft used NetBIOS for file sharing protocols like SMB. Hence, Novell had NDS (Novell Directory Services), but Microsoft (i think copied it ) and made AD (Active Directory), and since Windows 2000 the revolution had begun. Windows XP came alive. Ahh the times, yes I feel old.
Layers 5-7 I could understand why they were initially separated, because there used to be separate protocols for session management (5) and data transformation (6). I don't think the ordering of the upper 3 layers is as important anymore because now many things are just HTTP REST API's of some sort. Sessions are often managed by the application themselves by using Cookies, bearer tokens (JWT) or some other stateful/stateless implementation. And while TLS is regarded as a Layer 6 protocol, doing things like JSON, XML, YAML transformation can apply here too. I think the utility of being able to cram anything into a TCP connection on top of HTTP being a simple request/response model helped it gain popularity and with respect to an HTTP stack, separating "Application" into 3 layers is not very useful as it shouldn't concern Network Engineers who should be focused on layers 1-4. Just the same as how developers shouldn't be worried about bits-on-the-wire and how switches/routers work.
Good work, it was helpful and easy to understand. I also loved the small animations you created. for the suggestion I would say SSL and different kinds of it are confusing for me, I think it's worth a video. Thanks!
I always have an analogy in my head: a person sitting in a room without window, only communicate with the rest of world through a small hole. you can only send/receive go chess one by one. Then, how to solve problems like: information integrity, addressing, multiplexing etc? that’s the OSI model. In my opinion this analogy is quite accurate for electronics communication, meaning almost all these devices using wire and electrical signal to talk(Ethernet, TTL, SATA etc.) face to same problem/concept(or wireless connection mostly abstract a wire).
I love the way you have just explained things in details, as an ethical hacker/Pentester I love the small details which don't seems to matter but they matter a lot.👍👏👏
So a network has to be fairly local then? if its connected with an ethernet I imagine right? I'm not a techie but think I should be learning more about this stuff. Thank you in advance!
you are making me starting thinking i know everything about computers obviously I don't but dumbed down explanations like this makes it so everything just makes since and helps me understand better with what I don't know thanks for making these videos man : )
can you post some videos related to DOM XSS , CORS and CSRF and SSRF , File injection .Its technically bit complex to read from posrtswigger . How they work and work with different headers to find bug on servers?
I think with regard to physical layer, it would have been useful to say they have to be DIRECTLY connected. - So, either a wire directly connects the two devices, or for WiFi the radiowaves directly talk between the 2 antennas (on on device, one on the AP) etc - They have NO ability to "choose" who to send. They just set voltages in the physical world, and everyone "connected" reads the voltages. - It's not similar to a piece of paper, which you hand to someone specific. EDIT: Correct me if I'm wrong. I think technically, there probably is some control over it, and different sockets are not fully separated of course, but they are mostly, right?
Good video over all, but you got switches wrong. Switches operate based on physical address, refered to as Media Access Control (MACs). In the OSI model, that would be the layer two if OSI model. IP Adresses are logical representstion of "geological" (though not physical ) address and location of the device within a network. The higher levels of the network use the IP address (and many more things) to communicated with each other. The only thing Switches care about are MACs.
For me the term socket is really confusing file socket, network socket :), other topics: namespaces (network, cpu, file), containers, load, tracing (how does it work? instrumentation okay, but how do they do it actually, what is in the data application sends to for example jeager or datadog). SQL db stuff, useful metrics whatever, routing :)
What are some CTFs that you would recommend to learn about network security (port scanning, packet spoofing etc.)? I can't find any good CTFs except for the Network section of Root-Me.
Just a nitpick, a switch doesn't care about IP addresses usually, Ethernet works by routing MAC addresses and IP addresses are translated to MAC addresses using the ARP protocol
it sometimes is interesting to see the protocol in order to break it. It isn't always the application layer with the exploit, the protocol itself can also be vulnerable, such as sending strange URLs and URIs to a webserver attacking the http layer implementation, or SYN flooding or SYN port scanning attacking the TCP layer directly without any application ever knowing about that it's happening because a full connection is never made.
I think omitting the ARP protocol and MAC addresses and acting like typical layer2 Switches would look at the IP header was a bad idea in my opinion and might acutally be more confusing than helping people to understand the concept of layers. Acting like layers acutally work completely independet of each other like in the OSI model glosses over much of the complexity in reality.
sadly, we need to know how it works, due to NAT and some firewalls etc, and other things ... Indeed, if it just was a magical black box that always worked, we could ignore it ... but in reality ...
I did a web development official course and they wasted half a year teaching C and OSI models... yep, it's ok to don't know how those abstractions works, nice to know, but a waste of time for begginers.
I just start watching this video and I already gave a like for 2 reasons. First and more important it is a LIveOverflow video, so it is guarantee that it would be a super hight content quality Senconde and funniest, the work this guy did to record himself being a computer and send and receiving message hahahahaah
I'm a little confused as to why the addressing below the network (IP) layer was skipped, or at least why switches showed up in the "IP layer", rather than routers.
this is a great video, I created a huge interest after had problem in brazil with cyber crime, there you don't have laws against spying and the police don't have equipments to get hackers, I felt frustrated about this because a police told me this, after this I start studying this area to know more about protection and computer, now I'm studying a lot about this.
Again an awesome video! You really have a talent to explain things, thank you so much for this. Since you asked for a topic suggestion, I always struggle with certificates 🤷♂
Great video sir 👏👏 the hackers touch is super. please pick “sys calls” as topic for next as it is confusing to know how sys calls interacts with application in various operating systems. i vaguely know there is a lot of common things
Great explanation! Can you please make an explanation video on binary files? And how to to understand/make sense of them and manipulate them? How to read the specification of a binary file?
Less related to networking, but another video idea in this style might be explaining the difference between Encoding, Encryption, Hashing etc.
Those terms get misused a lot and are really useful to understand
Just like authentication and authorization
@@NoxiousPluK "auth"
@@overlisted Authentication*
@@Nunya58294 "auth"
Great idea!
This is a great explanation. Thank you!
Very nice vid, but it misses the data-link-layer, as computers still a point to point connection. But still, very cool vid, keep it up 😎
I love this channel.
anna nuvu devuvdave motham bale chepav ( you made it simple)
Please please please can you make a video about application layer or more specifically DNS and its hierarchy and types? Or routing explanation in a nonconfusing way?
Sorry if I asked maybe something unrelated to what you wanted to do
Can't wait for you to explain routing! This video was great :)
Been watching your content for a couple years now and I am absolutely floored with the change in quality and presentation you've made over time. I am excited to see what you create in the future. I have been a big fan of your Minecraft stuff, it used to be a big part of my life way back in the alpha days when a friend and I used to run a server.
Edit: The advertisement at the end was awesome!
@2:04 you made a cardinal mistake. Its not called a switch, its called a router, The IP Layer is layer 3 and the Physical Layer is Layer 1 and a Switch is a layer 2 device.
You forgot?
Oh you told it at 3:20 but its super important...
Sorry
Taking a minute to appreciate the video production quality with all that animations and actions in tile bars, OG work
You should've included 3:15 before you started explaining IPs. I was already about to comment you missed a layer xD
Nice one but in my opinion hiding the ethernet layer is a bit of an over simplification :/
In a real network without this concept you cannot understand the differences between switches and routers and the concept of routing is what people get more and more confused.
Good if it's a part 1 video. But not enough if you wanted it to be a deep dive
Great Video. Not detailed enough sadly but I still enjoyed it!
Please do more videos about networking :D
Good video, but extremely far from a "deepdive". The concept of OSI layers is the least deep idea in all of networking, by definition. :D
Good introduction though
I assume it is meant to be a part 1 video, kind of like I was making the same video pt 1 on my other channel (not going to advertise) but called it TCP for dummies. Otherwise it’s indeed the most basic info we learn in school. Very clean and pleasing though.
well, from a newbie's perspective its a pretty deep dive lol
@@OwO-. newbie here too. This vid was brilliant from my perspective--I see the terminology all the time, but haven't taken the time to define them. OP's comment makes me wonder about LiveOverflow's audience makeup. Btw, LO's CV is unquestionable and on display, so there's no doubt in him. Regardless, I appreciate him making videos like this, reaching down to a pleb like me to bring me up to speed.
Same! I trested OSI layers as blackboxes, as mentioned in the video, but could never find a wall-breaking introduction that would make sense. All the diagrams I've seen are much clearer after this vid.
I understand some people may find this offensively easy, but that wasn't the case for me and I really appreciate LO effort here
Layer 6 never looked this good! Amazing presentation!
Hey liveoverflow it would be nice if you can explain SSL and what is TCP socket and how to build one like you sometimes do in your videos.
I can see why you did it, but even implying for simplicity that switches look at IP addresses is definitely going to make any network admin cringe.
However, the main point of the video is that most hackers don't need to know how their packets are transmitted and just need to know general information about how the protocol works.
Since accepting abstraction as a hacker (most the time) appears to be the main thesis of this video, this video works. Networking can be a very dry topic. Networking 1 was the only class I've ever taken where the professor had to give us a 5 minute break in the middle so we didn't fall asleep. And that was only the first 3 of ~16 total credit hours worth of classes I needed on networking for my undergrad.
So tl;dr: This video is for hackers who don't know anything about networking. It is a deep dive, but networking is so deep a subject that this barely scratches the surface.
I just commented that I want a video on osi model for your video on http protocol. well my wish was granted 😂😊
Absolutely loving these Deepdive series
You can think of it like taking a letter and wrapping it in envelopes, with each envelope containing addressing information. First it gets wrapped in a TCP or UDP envelope, then that gets wrapped in an IP envelope, then THAT gets wrapped in an Ethernet or WiFi envelope, and then that gets passed to your mail courier.
Much better visual representation of what's actually going on imho
i would’ve like to have seen layers 4-7 covered, although in fairness that likely could’ve been it’s own video. i run a web server with multiple dns records pointing to the same server and am admittedly confused how it determines which subdomain is which for the server
the http host header, which gets added by your user agent (the browser, curl or other clients) when sending the request
Your videos I always look up to. Please make series on Networking. We are badly in need of it.
No IP in a switch.
Exactly, if you are a hacker, learn and ask questions yourself how it works. If you understand the basics very well of the OSI and TCP/IP layers then everything will makes sense to you. Networking is an art. In reality, you can write code to interact to your TCP/IP driver in Windows using Windows Sockets API, that interacts with Network Driver Interface Specification (NDIS) , that interacts with your NIC driver. So many abstractions ;) Do not forget, there are more protocols then TCP/IP, before we had IPX/SPX. Novell used NetBEUI and Microsoft used NetBIOS for file sharing protocols like SMB. Hence, Novell had NDS (Novell Directory Services), but Microsoft (i think copied it ) and made AD (Active Directory), and since Windows 2000 the revolution had begun. Windows XP came alive. Ahh the times, yes I feel old.
real hackers use linux because with windows all you see is black boxes (closed source)
Awww, I really hoped you'd explain OSI layers 5, 6, and 7. I never understood why they need to be separate.
I agree, a deeper dive into the other layers would be much appreciated.
Layers 5-7 I could understand why they were initially separated, because there used to be separate protocols for session management (5) and data transformation (6). I don't think the ordering of the upper 3 layers is as important anymore because now many things are just HTTP REST API's of some sort.
Sessions are often managed by the application themselves by using Cookies, bearer tokens (JWT) or some other stateful/stateless implementation. And while TLS is regarded as a Layer 6 protocol, doing things like JSON, XML, YAML transformation can apply here too.
I think the utility of being able to cram anything into a TCP connection on top of HTTP being a simple request/response model helped it gain popularity and with respect to an HTTP stack, separating "Application" into 3 layers is not very useful as it shouldn't concern Network Engineers who should be focused on layers 1-4. Just the same as how developers shouldn't be worried about bits-on-the-wire and how switches/routers work.
this was one of the best explanaition of how the TCP/IP protocol works. Thanks for it
I put a like just for the servers animations
Good work, it was helpful and easy to understand.
I also loved the small animations you created.
for the suggestion I would say SSL and different kinds of it are confusing for me, I think it's worth a video.
Thanks!
🙆🙇🙇 great explaination 🔥🔥🔥
I always have an analogy in my head: a person sitting in a room without window, only communicate with the rest of world through a small hole. you can only send/receive go chess one by one. Then, how to solve problems like: information integrity, addressing, multiplexing etc? that’s the OSI model. In my opinion this analogy is quite accurate for electronics communication, meaning almost all these devices using wire and electrical signal to talk(Ethernet, TTL, SATA etc.) face to same problem/concept(or wireless connection mostly abstract a wire).
Thank you, very helpful. 💕
This is not a deep dive but still a nice video
I love the way you have just explained things in details, as an ethical hacker/Pentester I love the small details which don't seems to matter but they matter a lot.👍👏👏
Skipping layer 2 is a nooo noooooo
So a network has to be fairly local then? if its connected with an ethernet I imagine right? I'm not a techie but think I should be learning more about this stuff. Thank you in advance!
you are making me starting thinking i know everything about computers obviously I don't but dumbed down explanations like this makes it so everything just makes since and helps me understand better with what I don't know thanks for making these videos man : )
😍😍 Thank you so much for making this video... I've always had confusion about it.
Ugh, IPv4, gross... It's 2023, start making tutorials in IPv6 by default, mentioning the legacy IPvGross as an option for legacy junk.
The LiveOverfont looks really good!
can you post some videos related to DOM XSS , CORS and CSRF and SSRF , File injection .Its technically bit complex to read from posrtswigger . How they work and work with different headers to find bug on servers?
I think with regard to physical layer, it would have been useful to say they have to be DIRECTLY connected.
- So, either a wire directly connects the two devices, or for WiFi the radiowaves directly talk between the 2 antennas (on on device, one on the AP) etc
- They have NO ability to "choose" who to send. They just set voltages in the physical world, and everyone "connected" reads the voltages.
- It's not similar to a piece of paper, which you hand to someone specific.
EDIT: Correct me if I'm wrong.
I think technically, there probably is some control over it, and different sockets are not fully separated of course, but they are mostly, right?
Kudos for kernel developers who wrote TCP/IP implementation overnight
Wah! Appreciate your effort. It's been years that i was thinking how tcp talking to tcp possible. You cleared out that abstraction.
Good video over all, but you got switches wrong. Switches operate based on physical address, refered to as Media Access Control (MACs). In the OSI model, that would be the layer two if OSI model.
IP Adresses are logical representstion of "geological" (though not physical ) address and location of the device within a network.
The higher levels of the network use the IP address (and many more things) to communicated with each other. The only thing Switches care about are MACs.
For me the term socket is really confusing file socket, network socket :), other topics: namespaces (network, cpu, file), containers, load, tracing (how does it work? instrumentation okay, but how do they do it actually, what is in the data application sends to for example jeager or datadog). SQL db stuff, useful metrics whatever, routing :)
Always great to watch your videos!
What are some CTFs that you would recommend to learn about network security (port scanning, packet spoofing etc.)? I can't find any good CTFs except for the Network section of Root-Me.
Just a nitpick, a switch doesn't care about IP addresses usually, Ethernet works by routing MAC addresses and IP addresses are translated to MAC addresses using the ARP protocol
I was about to shout on the comment "MAAAAC MAC ADDR MOST SWITCH WORK WITH MAC" 😂
Thanks for the vid
it sometimes is interesting to see the protocol in order to break it. It isn't always the application layer with the exploit, the protocol itself can also be vulnerable, such as sending strange URLs and URIs to a webserver attacking the http layer implementation, or SYN flooding or SYN port scanning attacking the TCP layer directly without any application ever knowing about that it's happening because a full connection is never made.
I find that I'm best at teaching the things I've struggled with myself -- apparently this isn't just true for me. Great video :)
I think omitting the ARP protocol and MAC addresses and acting like typical layer2 Switches would look at the IP header was a bad idea in my opinion and might acutally be more confusing than helping people to understand the concept of layers. Acting like layers acutally work completely independet of each other like in the OSI model glosses over much of the complexity in reality.
layered packets are scary
sadly, we need to know how it works, due to NAT and some firewalls etc, and other things ... Indeed, if it just was a magical black box that always worked, we could ignore it ... but in reality ...
They always teach OSI first! Didn’t click for me until I got in the field working haha
I did a web development official course and they wasted half a year teaching C and OSI models... yep, it's ok to don't know how those abstractions works, nice to know, but a waste of time for begginers.
Nice video! But I still don't understand the motivation or the technical requirement to distinguish between OSI-model layer 5, 6 and 7.
Thank you!
I just start watching this video and I already gave a like for 2 reasons.
First and more important it is a LIveOverflow video, so it is guarantee that it would be a super hight content quality
Senconde and funniest, the work this guy did to record himself being a computer and send and receiving message hahahahaah
I'm a little confused as to why the addressing below the network (IP) layer was skipped, or at least why switches showed up in the "IP layer", rather than routers.
this is a great video, I created a huge interest after had problem in brazil with cyber crime, there you don't have laws against spying and the police don't have equipments to get hackers, I felt frustrated about this because a police told me this, after this I start studying this area to know more about protection and computer, now I'm studying a lot about this.
Dude. Your explanations are fantastic. Congrats and thanks.
Again an awesome video! You really have a talent to explain things, thank you so much for this. Since you asked for a topic suggestion, I always struggle with certificates 🤷♂
A video on bash scripting would be nice- and especially how to interface a script for example to read/write to netcat
Exceptional work.
Everything made easy.
Hey man. Loved the video. You can also explain what exactly are Threads in another video...
Great video sir 👏👏 the hackers touch is super. please pick “sys calls” as topic for next as it is confusing to know how sys calls interacts with application in various operating systems. i vaguely know there is a lot of common things
Don't forget my ethernet cable and wifi router wrapped in a box and shipped in an Amazon truck.
Great video. Please make such kind of easy understanding video more on networking & (ssh, socket etc) stuffs
Very helpful video, also may I know which font are used to illustrate the pythom socket code ???
Thanks for making these videos. it really helped me to understand the concepts
Hey! You should make a Deepdive into how I2P works, I'd be really interested to know
BGP BGP BGP
this is amazing ...thanks for putting hardwork and making this great content free
You explained this way better than my uni prof. Thanks!
Id say this is very far from a deepdive! its more like a rough overview, with a few detours and examples of implementations.
i wish i accepted blackboxes, it drives me nuts whenever i dont understand something im using when creating programs
every where i go i find only theory and no coding of network i want to implement a adhoc network on stm32 using rf transceiver where i should begin
This is the perfect video for learning for my networking exam. Thanks! :D
Does anyone know any good books on computer networking for beginners ? Which ones are good ? Thanks in advance
Notice the effort of those small computer motions. This is why a computer can become old, and needs to be replaced with new young minions.
Please explain what a bus is. Talking about drivers could also be cool.
I like liveoverflow because this make me easy to understand
No, I don't think I will.
*starts using breadboards and only transistors*
TCP is nice. For the most part. It makes it so you dont have to think about networking. You just treat it as a black box
This is a really good video about networking. ❤️
Love the Deepdive series. Please, keep it up.
Parallelism and Synchronization primitives
Bro i hope he makes like really indef videos about some of this stuff its all so intresting and he makes it so anyone can understand it
Excellent explanation! Thank you so much.
you are a saviour why did you miss other layers? please explain all layers thanks
you explained this sooooo good. makes me understand more about what my uni prof was trying to explain for the past month or so in just 13 minutes
Does this mean every computer has a webserver running on port 80
3:02 sorry, but a switch doesn't look or care about IP addresses.
I like the "what to do with my hands" pose computers are idling on.
one of the best expalanation ive ever seen about ISO/OSI Modell
You make every thing easy to learn , Thank you for that i hope you never stop , i realy enjoy
Hello, this is a German coastguard....
Great explanation! Can you please make an explanation video on binary files? And how to to understand/make sense of them and manipulate them? How to read the specification of a binary file?
Check out the binary exploitation series........am sure it will scratch at least the surface
beautifully explained, thank you!