i remembered this please look one second

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I dont know what exam you mean, but YES. Even if you are only dealing with hardware this stuff is at the very core of how networks work. Each device operates at a certain level (sometimes more than one) of the OSI RM.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

That was probably me in a parallel thread to this one created by the same member. I agree with Freddy. kobem has been given more than enough good advice and answers to last quite awhile. It's up to him to actually start implemented what's been provided.

 

Stu's right... these are network fundamentals that you should already know WELL before advancing to more difficult stuff.

 

oh ok cool thanks

 

I think its important to understand how things work, if the OSI model helps then great if it doesn't then just remember its just a MODEL, its not the real world, go out and learn some real world stuff like TCP/IP and come back to it later....

You can buy a basic networking book for £10 and read it in a few days, this will give you enough knowledge to perform basic tasks, alot of the rest you can then learn as you go, if networking isn't your core skill that is...

 

Here is the theoretical OSI model. Use this to understand the various layers of simple networking.

Definition of TCP (and UDP if your getting into web, servers & ftp)

"TCP/IP (Transmission Control Protocol/Internet Protocol) is the basic communication language or protocol of the Internet. It can also be used as a communications protocol in a private network (either an intranet or an extranet). When you are set up with direct access to the Internet, your computer is provided with a copy of the TCP/IP program just as every other computer that you may send messages to or get information from also has a copy of TCP/IP.

TCP/IP is a two-layer program. The higher layer, Transmission Control Protocol, manages the assembling of a message or file into smaller packets that are transmitted over the Internet and received by a TCP layer that reassembles the packets into the original message. The lower layer, Internet Protocol, handles the address part of each packet so that it gets to the right destination. Each gateway computer on the network checks this address to see where to forward the message. Even though some packets from the same message are routed differently than others, they'll be reassembled at the destination.

TCP/IP uses the client/server model of communication in which a computer user (a client) requests and is provided a service (such as sending a Web page) by another computer (a server) in the network. TCP/IP communication is primarily point-to-point, meaning each communication is from one point (or host computer) in the network to another point or host computer. TCP/IP and the higher-level applications that use it are collectively said to be "stateless" because each client request is considered a new request unrelated to any previous one (unlike ordinary phone conversations that require a dedicated connection for the call duration). Being stateless frees network paths so that everyone can use them continuously. (Note that the TCP layer itself is not stateless as far as any one message is concerned. Its connection remains in place until all packets in a message have been received.)

Many Internet users are familiar with the even higher layer application protocols that use TCP/IP to get to the Internet. These include the World Wide Web's Hypertext Transfer Protocol (HTTP), the File Transfer Protocol (FTP), Telnet (Telnet) which lets you logon to remote computers, and the Simple Mail Transfer Protocol (SMTP). These and other protocols are often packaged together with TCP/IP as a "suite."

Personal computer users with an analog phone modem connection to the Internet usually get to the Internet through the Serial Line Internet Protocol (SLIP) or the Point-to-Point Protocol (PPP). These protocols encapsulate the IP packets so that they can be sent over the dial-up phone connection to an access provider's modem.

Protocols related to TCP/IP include the User Datagram Protocol (UDP), which is used instead of TCP for special purposes. Other protocols are used by network host computers for exchanging router information. These include the Internet Control Message Protocol (ICMP), the Interior Gateway Protocol (IGP), the Exterior Gateway Protocol (EGP), and the Border Gateway Protocol (BGP). "

Coutesy of TechTarget

 

Maybe it helps if you compare it to a normal post system.
You and your friend (application) write a number of letters in a mail exchange (presentation) on a piece of paper (session) and put it in an envelope (transport). The postman takes it, reads the address (network), puts it in his bag and delivers in in your friends mailbox (physical).
Now, the postman does not care what he delivers, you can put various thing in the envelope (the envelope does not care).
You could use a different protocol set (telephone, bring a visite). You could even use the letter and bring him yourself or fax it.

This exemple is not 100% correct, but I hope you see the light now.