Dear All,
I was posting on overclockers, and whilst some people were friendly, very quickly people started posting sh*tt* things.
So I thought I would try here again. I remember it was quite friendly before. I have been trying to work through COMPTIA, because I have recently changed course big time, career wise. I think the best way into working in networking is going in as first line support. So, I have also been working on the OSI and TCP/IP models. I tend to overthink stuff, and end up making it far harder than it actually is.
I found a web page which was pretty good putting the OSI model into context.
They make the OSI model into how car moves along. So it needs alternator, drive shaft, battery, gearbox, bla bla bla, and when it has all it need it will move along. I thought this wass good. This is the link https://www.practicalnetworking.net/series/packet-traveling/osi-model/
Basically I think it mean each layer is required on the network, and once the frame/packet gets all the info and 'stuff' it needs, layer by layer, it will be able to move along the network.
I am now looking into the TCP/IP - cloudflare does pretty good description, saying it like a puzzle that gets broken into pieces at the senders end, and sent out into lots of different envelopes, and the IP controls the address for each. They all take different routes, and then are assembled at the other end, when they all are there. TCP ensures the connection and the moving of the pieces, and then put them back together in order at the other end.
There was a lot of talk on other sites about each later being encapsulated by another. Like those dolls you could get that unscrewed in the middle, and there was another smaller doll, and within that another smaller doll. They are all identical, and unscrew the same way, but encapsulate each other.
So not sure about this one yet, but working on it.
If anyone has any ideas about how best to understand these things, I would be v grateful for your help. I have looked at Chuck networking, and Professer Messer - he doesn't explain TCP in a very clear fashion I don't think. Chuck is really cool, but he does go pretty quick when explaining those models.
Thanks for reading this small essay!
Matthew
I was posting on overclockers, and whilst some people were friendly, very quickly people started posting sh*tt* things.
So I thought I would try here again. I remember it was quite friendly before. I have been trying to work through COMPTIA, because I have recently changed course big time, career wise. I think the best way into working in networking is going in as first line support. So, I have also been working on the OSI and TCP/IP models. I tend to overthink stuff, and end up making it far harder than it actually is.
I found a web page which was pretty good putting the OSI model into context.
They make the OSI model into how car moves along. So it needs alternator, drive shaft, battery, gearbox, bla bla bla, and when it has all it need it will move along. I thought this wass good. This is the link https://www.practicalnetworking.net/series/packet-traveling/osi-model/
Basically I think it mean each layer is required on the network, and once the frame/packet gets all the info and 'stuff' it needs, layer by layer, it will be able to move along the network.
I am now looking into the TCP/IP - cloudflare does pretty good description, saying it like a puzzle that gets broken into pieces at the senders end, and sent out into lots of different envelopes, and the IP controls the address for each. They all take different routes, and then are assembled at the other end, when they all are there. TCP ensures the connection and the moving of the pieces, and then put them back together in order at the other end.
There was a lot of talk on other sites about each later being encapsulated by another. Like those dolls you could get that unscrewed in the middle, and there was another smaller doll, and within that another smaller doll. They are all identical, and unscrew the same way, but encapsulate each other.
So not sure about this one yet, but working on it.
If anyone has any ideas about how best to understand these things, I would be v grateful for your help. I have looked at Chuck networking, and Professer Messer - he doesn't explain TCP in a very clear fashion I don't think. Chuck is really cool, but he does go pretty quick when explaining those models.
Thanks for reading this small essay!
Matthew
