{"id":67,"date":"2011-11-22T19:57:53","date_gmt":"2011-11-22T19:57:53","guid":{"rendered":"http:\/\/microsoftgeek.com\/?p=67"},"modified":"2011-11-22T19:58:50","modified_gmt":"2011-11-22T19:58:50","slug":"how-the-network-access-layer-works","status":"publish","type":"post","link":"https:\/\/microsoftgeek.com\/?p=67","title":{"rendered":"How the Network Access Layer Works"},"content":{"rendered":"<p>The Network Access Layer it  is the layer responsible for interfacing with your network\u2019s  architecture- something the everyday user can\u2019t see. As we can\u2019t  physically interact with the Network Access Layer, how it works often  eludes networking students.<\/p>\n<p>If you haven\u2019t already, you may wish to read the previous section on  encapsulation- we will be reviewing part of the encapsulation again in  this section.<\/p>\n<h3>What the Network Access Layer Accomplishes<\/h3>\n<p>It may be poor for education, but the Network Access  Layer\u2019s invisibility to the everyday user means management of the layer  is unnecessary in most cases. Inventions such as the Universal Plug and  Play (known to early Windows users as \u201cPlug and Pray\u201d) enables users to  setup networked devices with little to no configuration.<\/p>\n<p>Behind the scenes, the Network Access Layer is responsible for  several things; including error checking, formatting data into frames,  and interfacing with network adapters. See the box below for the full  list of responsibilities of the Network Access Layer.<\/p>\n<p><strong>Responsibilities of the Network Access Layer<\/strong><\/p>\n<ul>\n<hr \/>\n<li> <strong>1.<\/strong> Checks for errors on incoming frames, and sends  error checking information on outgoing frames so receiving computers  can check for errors.<\/li>\n<li><strong>2.<\/strong> Acknowledgement of received frames is another  feature. If a frame isn\u2019t received correctly, it will be resent to the  appropriate destination.<\/li>\n<li><strong>3.<\/strong> Formats outgoing data into frames, and then  converts the data into electrical pulses for transmission. The receiving  computer will rebuild the frame, and send the data up to the next  layer.<\/li>\n<li><strong>4.<\/strong> Interfaces with network adapters and coordinates  data transmission with the selected network architecture. An Ethernet  network, for instance, will require different transmission methods than a  Token Ring network.<\/li>\n<hr \/>\n<\/ul>\n<h3>Dividing the Network Access Layer with the OSI Model<\/h3>\n<p>The TCP\/IP model only has four layers as compared to  the OSI model\u2019s seven. The Network Access Layer in particular is  subdivided into two separate layers in the OSI model. Because this aids  in learning, we will be working with the OSI model in this section. You  can see a visual diagram of the two models below.<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/www.learn-networking.com\/wp-content\/oldimages\/osi-model.jpg\" alt=\"osi model tcp\" \/><\/p>\n<p>We are now dealing with two layers: the Data Link Layer and the  Physical Layer. The Physical Layer is the layer responsible for turning  the data frame into a stream of bits. This breakdown of the frame into  bits is necessary for transmission. On the receiving end, the Physical  Layer rebuilds the bits into a frame.<\/p>\n<p>The Data Link Layer actually performs two different functions: Media  Access Control, or MAC, and Logical Link Control, or LLC. The Media  Access Control is the sublayer that provides an interface with the  network adapter, otherwise known as your Network Interface Card or NIC.  This card holds your MAC address, which is burned into your Network  Interface Card at the factory of which it was made.<\/p>\n<p>The Logical Link Control is the sublayer that performs error checking  for frames. It also manages links between devices that are  communicating over a subnet. It also offers flow control and  acknowledgement of delivery.<\/p>\n<h3>Physical Addressing<\/h3>\n<p>Physical addressing is the aspect of the Network Access  Layer that relates physical addresses to logical addresses. This is  nothing more than simply converting your MAC address to an IP address  for easier use in management.<\/p>\n<p>Data sent across a network uses the physical address, so why not just  use the physical address as compared to a logical address? Among other  reasons, the physical address is too lengthy for practical use by  humans. In the case of an Ethernet network, it is 48 bits long.<\/p>\n<p>To actually go from a physical address to a logical address (or vice  versa), we need to use ARP and RARP. Address Resolution Protocol and  Reverse Address Resolution Protocol can relate IP addresses to physical  addresses. These protocols function largely on the Internet Layer, so  we\u2019ll come back to them in our next section.<\/p>\n<h3>Dissecting a Frame of Data<\/h3>\n<p>As a short review, we know that the Network Access  Layer accepts a datagram from the Internet Layer, creates a frame, and  then grinds the frame down into electrical pulses for transmission. But  what we haven\u2019t covered is what the frame is exactly- but you\u2019re in  luck, there is a handy diagram shown below.<\/p>\n<p><img decoding=\"async\" src=\"http:\/\/www.learn-networking.com\/wp-content\/oldimages\/tcp-ip-frame.jpg\" alt=\"tcp ip frame\" \/><\/p>\n<p>While most of the above fields are self-explanatory, the frame check  sequence, or FCS, needs some explanation. This is a means of verifying  data transmissions. The sending computer calculates what is called a  Cyclical Redundancy Check, or CRS, and sends the calculation with the  frame. If the receiving computer performs the CRS calculation and it  matches, all the data is present. Otherwise, data was lost in the  transmission. Don\u2019t worry if this is confusing to you- we\u2019ll review it  more in later chapters.<\/p>\n<p>Also, a good think to take note of is that each frame can only be  between 64 bytes and 1,518 bytes in size. This, however, does not  include the preamble\u2019s size in the measurement. If the data being sent  is larger than this, the information must be broken down into individual  frames; of which will be rebuilt at the receiving computer.<\/p>\n<h3>Closing Comments<\/h3>\n<p>The Network Access Layer accomplishes a lot for being nearly  invisible to the everyday computer user. It\u2019s such a large topic, in  fact, that we are overjoyed models like the OSI model could split it up  into two separate layers.<\/p>\n<p>We now know that the Network Access Layer interfaces with different  network types (such as Ethernet or Token Ring configurations), performs  error checking via the Frame Check Sequence, and is ultimately  responsible for getting information to its destination.<\/p>\n<p>The Network Access Layer is just one layer of the TCP\/IP model,  however- and in our next section we will be taking a closer look at  logical addressing at its finest- the Internet Layer!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Network Access Layer it is the layer responsible for interfacing with your network\u2019s architecture- something the everyday user can\u2019t see. As we can\u2019t physically interact with the Network Access Layer, how it works often eludes networking students. If you haven\u2019t already, you may wish to read the previous section on encapsulation- we will be [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","hentry","category-networking-stuff"],"_links":{"self":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/67","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=67"}],"version-history":[{"count":2,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/67\/revisions"}],"predecessor-version":[{"id":69,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=\/wp\/v2\/posts\/67\/revisions\/69"}],"wp:attachment":[{"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microsoftgeek.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}