:-(

[Orangeb]

OK, call me needy, or whatever, but I'm worried I'm not picking up this networking stuff quickly enough.



My parents and teachers used to say I always looked for a more complicated answer to a simple problem. But then I got an A*A* in science- so that was that!
But I think I did this with the OSI model with layers 2 and 3, rather than just accepting the networks need both!

Currently I'm doing that with the HTTP stuff- trying to find metaphor for it.
Any opinions on all this might help?

 

[Orangeb]

I have not contributed to other threads because I don’t know enough to do so. Anyway, I didn’t realise I had to do so to stay on the site.
If no-one took on anyone because they didn’t have any experience, how would any new generation move through any subject anywhere?
I thought I would try and get a decent understanding of networking, as well as knowing enough for a 1st line support job. That’s why I am doing the physical stuff with my cousin. I have not asked to be spoon fed, I have been learning and then asking if I get stuck, and over think stuff. Anyway, I don’t want a debate about my posts on here - I feel **** enough as it is. If you really must know why it’s taking a while - I have something called bi polar, and some days I don;’t do any learning, because of other stuff that gets in the way.

 

[Orangeb]

Cool - Thank you for your help. Yeah I was looking at the COMP TIA with a guy called Professor Messer, who takes you through it bit by bit on YouTube. He was explaining something and it wasn’t that clear, so i posted something on here, and one person said try chuck networking - thats how I came across that. I think I have just ‘attacked’ stuff on a far too thinly spread approach - the physical stuff, and how to set up a basic network - switches, routers, servers, virtual machines - most of which I can do. Then the OSI model, and then the comp tia, then definitions of things - DNS servers, DHCP, etc etc. I’ll go back to COMP tia and carry on through that, and when he talks about various models, if I don’t like his way of explaining it, I’ll use something else for that bit. I did have a networking for dummies book years ago. I’ll buy another one I think.
I think I could handle most of a first line support job - it would have to be basic, but I always just thought they would want a decent networking knowledge.
But my knowledge at moment is basic.

 

[Orangeb]

This is Professor Messers explanation of basic IP etc. I just found it hard to stop there, as his metaphor wasn’t great - So i went looking at got caught up again with the OSI model.

He goes from basic mobile phone stuff to a break down of Ethernet, and IP, and then TDP and UDP, with a mention of the layer 4 too. I’m thinking I can’t be the only person with basic knowledge to suddenly think “wow, brakes!!”.

 

[Orangeb]

OK, cool thanks AlphariusOmegan. I’ll look at getting them. I have put into YouTube, basic breakdown of Ethernet and IP.
From what I can see Ethernet is a protocol (rather than just a cable), and we send packet using this (which I knew about packets anyway). Packet have a IP payload, as well as others info. It says it’s a IEEE protocol. TDP and UDP are ways and rules (if you like), to send packets - TDP being more reliable as it can do things like tell the other ‘side’ to slow it down if they are sending data too fast, where UDP is less reliable, but faster, as it can’t do things like that.

 

[Orangeb]

I learnt a bit about packets when I first started ‘digging’ about, without any idea of what to learn first. There are so many videos and things out there that complicate basic stuff- so I’m sitting there going WTF - because up until recently Ethernet was just a cable plugged into my TV going to my router. Not quite sure how Ethernet is classed as a protocol AND people refer to an Ethernet cable - which is physical. That then leads into the 1st layer of OSI.

But also no-one explains why you have Ethernet IEEE Protocl and then another protocol TDP or UPD. I guess they are within a packet, rather than a more ‘overall’ protocol.

Oh ok, done some more searching, and I think what I am getting at it the packet is sent, and TCP or UDP are at one layer (so one protocol), and at a lower level is Ethernet IEEE protocol.

Sorry for the 6,0000000 little update notes!

I think the problem is when I decided to try and get into 1st line support ( 6 months ago), I took myself and effectively dropped me into the driving seat of a car on a motorway, and said “drive”, when I didn’t know what a car even was!!

 

[Orangeb]

OK, thank-you Felon. I agree actually. I went back to something basic I read when I first strarted looking at this whole subject, about what a packet is. I drew a diagram when I was round my cousins, last night, and put the various breakdown headers onto it - IP, TCP, UDP, HTTP, Ethernet - and said to him “ok, so where is the data? They are all protocols, just rules for doing something effectively” and he said that is just the header. The “payload” is underneath (in the diagram). I thought it’s like a missile - they have their rules - heat seeking, radar (whatever they use), and then they have thier payload behind. They actually call it a payload as well.
So thats a start. He also said ‘they’ only need 1 protocol - so the others would be discarded.