Before we discuss commercial Ethernet applications, let’s separate the terms between Ethernet and IP protocols.
When the majority of people think of Ethernet, we think in regards to a physical link.
You may have an Ethernet port on your computer system in which you connect in a cord that then connects to a router or button. This connection type is usually called a LAN connection.
Nevertheless, ethernet is [ethernet คือ, which is the term in Thai] not a link kind; however, rather, an IEEE protocol.
In our daily use of the internet we generally simply say that we are attached via Wireless or Ethernet. It’s a lot easier to say Ethernet than to get involved in the weeds of the actual regards to link methods, layers, stacks,and the like.
Now that we have stated that Ethernet is a protocol versus a physical connection, let’s get a little into the weeds of some of the terms.
Most interactions with our tools or computerstraverse several networks via something called a “package.”
Since there is a wide variety of devices that might wish to send and/or obtain information there need to be some common regulations for sending out and obtaining these packets. This is where the Ethernet “procedure” comes.
Amongst the most commonly known methods is the TCP/IP procedure. This procedure is extensively utilized in internet communications.
The term TCP/IP associates with TCP or “Transmission Control Protocol”, where the IP is “Internet Protocol.”
There are other protocols such as “Open System Affiliation” or OSI; however, for simpleness purpose, let’s stick with TCP/IP in the meantime.
The TCP/IP is a layered method. Those layers are:
Standard functions are described yet there are many, numerous information in each layer.
Each layer has a feature that it executes, as well as when complete, is then passed to the following layer.