{"id":280,"date":"2007-08-04T18:03:00","date_gmt":"2007-08-04T10:03:00","guid":{"rendered":"http:\/\/www.akuadi.org\/?p=6"},"modified":"2007-08-04T18:03:00","modified_gmt":"2007-08-04T10:03:00","slug":"media-access-control-mac-addresse","status":"publish","type":"post","link":"https:\/\/akuadi.org\/life\/blog\/2007\/08\/04\/media-access-control-mac-addresse\/","title":{"rendered":"Media Access Control &#8211; MAC Addresse"},"content":{"rendered":"<div align=\"center\">\n<h3 class=\"page_title\">Media Access Control &#8211; MAC Addresses<\/h3>\n<h5>Introduction<\/h5>\n<p align=\"left\"><span style=\"color:#ffff00;\">Media Access Control<\/span> (<span style=\"color:#ffffff;\"><span style=\"color:#ffff00;\">MAC<\/span><\/span>)              <span style=\"color:#ffffff;\"><span style=\"color:#ffff00;\">addresses<\/span><\/span>              are talked about in various sections on the site, such as the OSI-Layer              2, Multicast, Broadcast and Unicast. We are going to analyse them              in depth here so we can get a firm understanding of them since they              are part of the fundamentals of networking.<\/p>\n<p align=\"left\"><span style=\"color:#ffff00;\">MAC addresses<\/span> are physical              addresses, unlike IP addresses which are logical addresses. Logical              addresses require you to load special drivers and protocols in order              to be able to configure your network card\/computer with an IP Address,              whereas a MAC address doesn&#8217;t require any drivers whatsoever. The              reason for this is that the <span style=\"color:#ffffff;\"><span style=\"color:#ffff00;\">MAC              address<\/span><\/span> is actually &#8220;burnt-in&#8221; into your network              card&#8217;s memory chipset. <\/p>\n<p align=\"left\"><span style=\"color:#ff99ff;\"><b>The Reason for MAC<\/b><\/span><\/p>\n<p align=\"left\">Each computer on a network needs to be identified in              some way. If you&#8217;re thinking of IP addresses, then you&#8217;re correct              to some extent, because an IP address does identify one unique machine              on a network, but that is not enough. Got you mixed up? <\/p>\n<p align=\"left\">Check the diagram and explanation below to see why :<\/p>\n<p align=\"center\"><img fetchpriority=\"high\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/mac-addresses-1.gif\" height=\"287\" width=\"431\" \/><\/p>\n<p align=\"left\">You see, the IP address of a machine exists on the<span style=\"color:#00ff00;\">              3rd Layer<\/span> of the OSI model and, when a packet reaches the computer,              it will travel from<span style=\"color:#00ffff;\"> Layer 1<\/span> upwards,              so we need to be able to identify the computer before <span style=\"color:#00ff00;\">Layer              3<\/span>.<\/p>\n<p align=\"left\">This is where the<span style=\"color:#ffff00;\"> MAC address<\/span>              &#8211; <span style=\"color:#ffff00;\">Layer 2<\/span> comes into the picture. All              machines on a network will listen for packets that have their MAC              address in the destination field of the packet (they also listen for              broadcasts and other stuff, but that&#8217;s analysed in other sections).              The <span style=\"color:#00ffff;\">Physical Layer<\/span> understands the electrical              signals on the network and creates the frame which gets passed to              the <span style=\"color:#ffff00;\">Datalink layer<\/span>. If the packet is              destined for the computer then the <span style=\"color:#ffff00;\">MAC address<\/span>              in the destination field of the packet will match, so it will accept              it and pass it onto the <span style=\"color:#00ff00;\">Layer above<\/span> (<span style=\"color:#00ff00;\">3<\/span>)              which, in turn, will check the network address of the packet (IP Address),              to make sure it matches with the network address to which the computer              has been configured.<\/p>\n<p align=\"left\"><span style=\"color:#33ffff;\"><b>Looking at a MAC<\/b><\/span><\/p>\n<p align=\"left\">Let&#8217;s now have a look at a <span style=\"color:#ffff00;\">MAC              address<\/span> and see what it looks like! I have taken my workstations              MAC address as an example:<\/p>\n<p align=\"center\"><img decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/mac-addresses-2.gif\" height=\"94\" width=\"354\" \/><\/p>\n<p align=\"left\">When looking at a MAC address, you will always see it              in HEX format. It is very rare that a MAC address is represented in              Binary format because it is simply tooooo long as we will see futher              on. <\/p>\n<p align=\"left\">When a vendor, e.g Intel, creates network cards, they              don&#8217;t just give them any <span style=\"color:#ffff00;\">MAC address<\/span>              they like, this would create a big confusion in identifying who created              this network card and could possibly result in clashing with another              MAC address from another vendor e.g D-link, who happened to choose              the same MAC address for one of their network cards !<\/p>\n<p align=\"left\">To make sure problems like this are not experienced,              the IEEE group split the <span style=\"color:#ffff00;\">MAC address<\/span>              in half, and used the<span style=\"color:#66ff00;\"> first half<\/span> to identify              the vendor, and the <span style=\"color:#ff99ff;\">second half<\/span> is for              the vendor to allocate as serial numbers:<\/p>\n<p align=\"center\"><img decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/mac-addresses-3.gif\" height=\"118\" width=\"248\" \/><\/p>\n<p align=\"left\">The <span style=\"color:#66ff00;\">Vendor code<\/span> is specified              by RFC &#8211; 1700. You might find a particular vendor having more than              just one code; this is because of the wide range of products they              might have. They just apply for more, as they need ! <\/p>\n<p align=\"left\">Keep in mind that even tho the <span style=\"color:#ffff00;\">MAC              address<\/span> is &#8220;burnt-in&#8221; to the network card&#8217;s memory,              some vendors will allow you to download special programs to change              the <span style=\"color:#ff99ff;\">second half<\/span> of the <span style=\"color:#ffff00;\">MAC              address<\/span> on the card. This is because the vendors actually reuse              the same MAC addresses for their network cards because they create              so many that they run out of numbers ! But at the same time, the chances              of you buying two network cards which have the same MAC address are              so small that it&#8217;s almost impossible ! <\/p>\n<p align=\"left\"><span style=\"color:#ffff00;\"><b>Let&#8217;s start talking bits and              bytes!<\/b><\/span><\/p>\n<p align=\"left\">Now that we know what a MAC address looks like, we need              to start analysing it. A MAC address of any network card is always              the same length, that is, <span style=\"color:#ffffff;\"><span style=\"color:#00ffff;\">6              Bytes<\/span><\/span> long or <span style=\"color:#ffffff;\"><span style=\"color:#00ffff;\">48              Bits<\/span><\/span> long. If you&#8217;re scratching your head wondering              where these figures came from, then just have a look at the picture              below which makes it a bit easier to understand:<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/mac-addresses-4.gif\" height=\"312\" width=\"482\" \/><\/p>\n<p align=\"left\">So that completes the discussion regarding<span style=\"color:#ffff00;\">              MAC Addresses<\/span>! I hope you have understood it all because it&#8217;s              very important so you can expand your knowledge and truly understand              what happens in a network !<\/p>\n<p><\/p>\n<p align=\"left\"><\/p>\n<p align=\"left\"><span style=\"font-weight: bold;\">Source &amp; Credit to<\/span> : <a href=\"http:\/\/www.firewall.cx\/\" target=\"_blank\" rel=\"noopener\">http:\/\/www.firewall.cx\/<\/a><\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Media Access Control &#8211; MAC Addresses Introduction Media Access Control (MAC) addresses are talked about in various sections on the site, such as the OSI-Layer 2, Multicast, Broadcast and Unicast. We are going to analyse them in depth here so we can get a firm understanding of them since they are part of the fundamentals [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-280","post","type-post","status-publish","format-standard","hentry","category-data-transmissions"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/posts\/280","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/comments?post=280"}],"version-history":[{"count":0,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/posts\/280\/revisions"}],"wp:attachment":[{"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/media?parent=280"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/categories?post=280"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/tags?post=280"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}