![]() ![]() The client doesn't need to know or care about the destination MAC unless it's communicating directly with it and there are no routers involved. The network gear at the other end sorts out the ARP and routes the packet appropriately once it reaches the destination broadcast domain. Outside of that it's been routed and this is done with a TCP/IP (and rarely IPX) address encoded in the packet headers. Unfortunately ARP is only maintained and available within the broadcast domain. Once you've communicated you need only to look up the MAC in your local ARP cache to address non routed packets. Any time you connect to a device over the network, within your broadcast domain, (often your subnet) you add that remote device's MAC to your ARP cache (aka table). Much like a sort of wire level DNS, ARP stores a IP to MAC mapping in the arp cache in the network gear and stations. TCP IP was created to allow routing between broadcast domains, as opposed to enlarging them (a la bridging) The IP address is easier and more logical for humans to route, deal with and organize in a much more orderly fashion than could be done with MAC (considering how ethernet works and the intended use of the MAC). See the mac address is how wire level network addressing happens.
0 Comments
Leave a Reply. |