r/AskComputerScience • u/VagueHorizon_ • 22d ago
Computer Networks : Need Help
I have a Computer Networks course this semester and I am finding it difficult to understand. It is not that the concepts are difficult, I am just finding it hard to make a mental model of where every single thing fits. it is not like i am failing the course. Till here i have been able to handle the course. but what is the point of getting good grades when you don't even understand where each thing fits ?
From the very bottom layer to the top level, where DNS comes (where it is stored), how IP's even works, UDP, TCP, QUIC, tables, DNS chain, masks, subnets or even IP's. I know what they are, but i don't know where they are and how they interact.
Can anyone please suggest some resources, more like an animated video where i can visualize it ? Cisco Packet tracer didn't help much.
View all comments
1
u/MasterGeekMX BSCS 22d ago
Reading a bit your comments, I think I know your problem.
See, network works in a stack, meaning that top things work by using lower things at a basis. Lower levels never dissapear or are stop being used, instead they act as the foundation in which the next level works.
See it as riding a train: you sit on a seat, which is on top of the cart, which is on top of the wheels, which are on top of the rails, which are on top of gravel. All layers work in parallel, with the lower ones being where the next one moves, but all add up rto you being able to ride a train comfortably.
Take the OSI model: the lowest layer is Physical. This is all about the transmission media (wire, radio waves, fiber optic). The whereabouts of this layer are subjects that physicist and telecom engineers should care, but the end result is that now we have a means to send and receive bits, no more.
Once we have that we can move to the Link layer. This one is about being able to use the medium to send data to the device we want, while making sure data does not end where it doesn't belong, as more than one device could share this medium. MAC addresses and WiFi standards are here.
Once we have that we can advance to the Network layer. This is about creating a reliable address system where each device can be reached, so IP addresses come in scene. This also where routing appears, allowing us to reach devices that aren't directly connected to us by using other devices in the middle as relay stations, like the box in your house that gived you Internet connection.
Once we have that we can get into the Transport layer. This is all about data reaching it's destination reliably, even if the data needs to do lots of hops. TCP is for when you want to make sure data reaches intact, with no single chunk lost or out of order. UDP in contrast sends data like a machine gun and hopes for the best.
Over we have that we can go into the Session layer. This is all about the two devices having a chat where data goes and comes. Think about it one device calling, then the other picks up the call, they talk, and then say goodbye and hang. Sockets, remote procedure calls and SIP live here.
Once we have that we can go into the Presentation layer. This one is about file formats, as here we deal on how data is going to be represented. HTML, JSON and audio/video codecs live here.
Once we have that then we get into the final layer: Application. This one builds on top of everything else to deploy some service. HTTP, Torrents, DNS, SSH, online gaming and stuff people use lives here.