{"id":284,"date":"2007-08-04T18:08:00","date_gmt":"2007-08-04T10:08:00","guid":{"rendered":"http:\/\/www.akuadi.org\/?p=10"},"modified":"2007-08-04T18:08:00","modified_gmt":"2007-08-04T10:08:00","slug":"data-transmission-broadcast","status":"publish","type":"post","link":"https:\/\/akuadi.org\/life\/blog\/2007\/08\/04\/data-transmission-broadcast\/","title":{"rendered":"Data Transmission &#8211; Broadcast"},"content":{"rendered":"<table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" width=\"630\">\n<tbody>\n<tr>\n<td colspan=\"3\" height=\"958\" valign=\"top\">\n<div align=\"center\">\n<h3 class=\"page_title\">Data Transmission &#8211; Broadcast<\/h3>\n<h5 align=\"left\">Introduction<\/h5>\n<p align=\"left\">The term &#8220;<span style=\"color:#ffff00;\">Broadcast<\/span>&#8221;              is used very frequently in the networking world . You will see it              in most networking books and articles, or see it happening on your              hub\/switch when all the LED&#8217;s start flashing at the same time ! <\/p>\n<p align=\"left\">If you have been into networking              for a while you most probably have come across the terms &#8220;<span style=\"color:#ffff00;\">broadcast<\/span>&#8221;              and &#8220;<span style=\"color:#ff66cc;\">subnet broadcast<\/span>&#8221; . When              I first dived into the networking world, I was constantly confused              between the two, because they both carried the &#8220;broadcast&#8221;              term in them. We will analyse both of them here, to help you understand              exactly what they are and how they are used ! <\/p>\n<\/p><\/div>\n<div align=\"center\">\n<p align=\"left\"><span style=\"color:#ffff00;\"><b>Broadcast <\/b> <\/span><\/p>\n<p align=\"left\">A Broadcast means that the network              delivers one copy of a packet to each destination. On bus technologies              like Ethernet, broadcast delivery can be accomplished with a single              packet transmission. On networks composed of switches with point-to-point              connections, software must implement broadcasting by forwarding copies              of the packet across individual connections until all switches have              received a copy. We will be focusing only on Ethernet broadcasts.<\/p>\n<p align=\"left\">The picture below illustrates              a router which has sent a broadcast to all devices on its network:<\/p>\n<p align=\"center\"><img fetchpriority=\"high\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast%20network.gif\" height=\"255\" width=\"480\" \/><\/p>\n<p align=\"left\">Normally, when the computers on              the network receive a packet, they will first try to match the MAC              address of the packet with their own and if that is successful, they              process the packet and hand it to the OSI layer above (Network Layer),              if the MAC address is not matched, then the packet is discarded and              not processed. However, when they see a MAC address of <span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>,              they will process this packet because they recognise it as a broadcast.<\/p>\n<p align=\"left\">But what does a &#8220;<span style=\"color:#ffff00;\">broadcast<\/span>&#8221;              look like ? <\/p>\n<p align=\"left\">Check out the image below, which is taken from my packet              sniffer:<\/p>\n<p align=\"center\"><img decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast%202.gif\" height=\"37\" width=\"507\" \/><\/p>\n<p align=\"left\">Let&#8217;s now have a closer look at the above packet:<\/p>\n<\/p><\/div>\n<\/td>\n<\/tr>\n<tr>\n<td height=\"422\" valign=\"top\">The          image above shows a broadcast packet. You can clearly see that the &#8220;MAC          destination address&#8221; is set to <span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>.          The &#8220;Address IP destination&#8221; is set to <span style=\"color:#00ffff;\">255.255.255.255<\/span>,          this is the IP broadcast address and ensures that no matter what IP address          the receiving computer(s) have, they will not reject the data but process          it.  <\/p>\n<p align=\"left\"><span style=\"color:#ff9966;\">Now you might ask yourself<\/span>            &#8220;Why would a workstation want to create a broadcast packet ?&#8221;<\/p>\n<p align=\"left\">The            answer to that lies within the various protocols used on our networks            !<\/p>\n<p align=\"left\">Let&#8217;s            take for example <span style=\"color:#ffcc33;\">Address Resolution Protocol<\/span>,            or <span style=\"color:#ffcc33;\">ARP<\/span>. <span style=\"color:#ffcc33;\">ARP<\/span>            is used to find out which MAC address (effectively , which network card            or computer) has a particular IP address bound to it. You will find            a detailed example of the whole process in the <a href=\"http:\/\/www.firewall.cx\/ip_routing.php\" target=\"_blank\" rel=\"noopener\">IP            Routing section<\/a>.<\/p>\n<\/td>\n<td colspan=\"2\" valign=\"top\">\n<div align=\"center\"><img decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast-3.gif\" height=\"422\" width=\"291\" \/>          <\/div>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\" height=\"1013\" valign=\"top\">\n<p align=\"left\">For a network            device such as a router to ask &#8220;Who has IP address 192.168.0.100            ? &#8220;, it must &#8220;shout&#8221; it out so it can grab everyone&#8217;s            attention, which is why it will use a broadcast to make sure everyone            listens and processes the packet on the network. <\/p>\n<p align=\"left\">In the example image above, the particular machine was            looking for a DHCP server (notice the &#8220;bootps&#8221; protocol under<span style=\"color:#00ffff;\">            the UDP Header &#8211; Layer 4<\/span>, which is basically DHCP).<\/p>\n<p align=\"left\"><span style=\"color:#ff66cc;\"><b>Subnet Broadcast<\/b><\/span> or            <span style=\"color:#ff66cc;\"><b>Direct Broadcast<\/b><\/span>        <\/p>\n<p align=\"left\">A <span style=\"color:#ff66cc;\">Subnet<\/span> or <span style=\"color:#ff66cc;\">Direct            broadcast <\/span>is targetted not to all hosts on a network, but to            all hosts on a subnet. Since a physical network can contain different            subnets\/networks e.g 192.168.0.0 and 200.200.200.0, the purpose of this            special broadcast is to send a message to all the hosts in a particular            subnet.<\/p>\n<p align=\"left\">In the example below, <span style=\"color:#00ff00;\">Router A<\/span>            sends a subnet broadcast onto the network. <span style=\"color:#33ffcc;\">Hosts            A<\/span>,<span style=\"color:#33ffcc;\">B<\/span>,<span style=\"color:#33ffcc;\">C<\/span>            and the <span style=\"color:#ff3300;\">Server<\/span> are configured to be part            of the 192.168.0.0 network so they will receive and process the data,            but <span style=\"color:#33ffcc;\">Host D<\/span> is configured with a different            IP Adress, so it&#8217;s part of a different network, it will accept the packet            cause of its<span style=\"color:#ffff00;\"> broadcast MAC address<\/span>, but            will drop the packet when it reaches its <span style=\"color:#33ffff;\">Network            Layer<\/span>, where it will see that this packet was for a different            IP network.<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast-subnet-brdcst-3.gif\" height=\"312\" width=\"624\" \/><\/p>\n<p align=\"left\">It is very similar to the network broadcast we just talked            about but varies slightly in the sense that its IP broadcast is not            set to 255.255.255.255 , but is set to the subnet broadcast address.            For example, my home network is a Class C network : 192.168.0.0 with            a subnetmask of 255.255.255.0 or, if you like to keep it simple, : 192.168.0.0\/24.<\/p>\n<p align=\"left\">This means that the available valid hosts for this network            are from 192.168.0.1 to 192.168.0.254. In this Class C network, as in            every other network, there are 2 addresses which I can&#8217;t use. The first            one is preserved to identify the network (192.168.0.0) and the second            one for the<span style=\"color:#ff99ff;\"> subnet broadcast<\/span> (192.168.0.255).          <\/p>\n<p a\nlign=\"left\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast-subnet-brdcst-2.gif\" height=\"38\" width=\"630\" \/><\/p>\n<p align=\"left\">The above packet, captured from my packet sniffer, shows            my workstation broadcasting to the subnet 192.168.0.0. From the broadcast            address you can tell that I am using a full Class C network range, otherwise            the Destination IP wouldn&#8217;t be 192.168.0.255.<\/p>\n<p align=\"left\">\n<\/td>\n<\/tr>\n<tr>\n<td height=\"359\" valign=\"top\">\n<p>The Packet decoder on the right shows            you the contents of each header from the above packet.<\/p>\n<p>Looking at the MAC Header (Datalink Layer), the destination MAC address            is set to <span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>:<span style=\"color:#00ffff;\">FF<\/span>            and the IP Header (Network Layer) has the Destination IP set to 192.168.0.255            which is, as I said, the <span style=\"color:#ff66cc;\">Subnet<\/span> <span style=\"color:#ff66cc;\">Broadcast            <\/span>Address. Again, all computers on the network which are part of            the 192.168.0.0 subnet will process this packet, the rest will drop            the packet once they see it&#8217;s for a network to which they do not belong.<\/p>\n<p>In this example, I double clicked at my &#8220;Network Places&#8221;            and was searching for a computer, this forced my workstation to send            out a <span style=\"color:#ff66cc;\">Subnet Broadcast<\/span> on the network asking            if a particular computer existed on the network.<\/p>\n<\/td>\n<td width=\"15\"><\/td>\n<td valign=\"top\" width=\"313\">\n<div align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.firewall.cx\/pictures\/broadcast-subnet-brdcst.gif\" height=\"359\" width=\"290\" \/><\/div>\n<\/td>\n<\/tr>\n<tr>\n<td colspan=\"3\" height=\"61\" valign=\"top\">\n<p>And that just about does it for the broadcasting section !<\/p>\n<p><\/p>\n<p><\/p>\n<p><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<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Data Transmission &#8211; Broadcast Introduction The term &#8220;Broadcast&#8221; is used very frequently in the networking world . You will see it in most networking books and articles, or see it happening on your hub\/switch when all the LED&#8217;s start flashing at the same time ! If you have been into networking for a while you [&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-284","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\/284","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=284"}],"version-history":[{"count":0,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/posts\/284\/revisions"}],"wp:attachment":[{"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/media?parent=284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/categories?post=284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/akuadi.org\/life\/wp-json\/wp\/v2\/tags?post=284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}