Each of these ranges have been specially designated for private network use, so you can be sure that no other public server (e.g. When configuring IP addresses, you are likely to run across addresses of the form 10.x.x.x, .x, or 172.x.x.x. A detailed discussion of NAT is beyond the scope of this tutorial. In addition, since there are more than 2^32 connected Ethernet devices on the planet, IP addresses can be reused across multiple smaller networks while those machines are still accessible via a process called Network Address Translation (NAT). Using this pattern, small groups of computers can communicate with each other with only local traffic, therefore reducing data collisions in the larger network.
#YOUTUBE.COM SUBNET MASK TABLE MAC#
Whereas MAC addresses do not typically follow a pattern in a given set of machines (they are randomly distributed by vendor), since IP addresses are user-configurable they can be set up to follow a logical, hierarchical pattern. This simple idea has significant benefits. Since IP addresses can be assigned to individual NICs by the user, it is possible to assign similar IP addresses to a group of interfaces and then easily determine whether a given IP address is inside or outside of the local network. Sample rule: all interfaces with IP addresses in the range 192.168.100.0 to 192.168.100.255 are inside of the local network, and interfaces with other addresses are outside. If all machines follow a rule where all addresses with format are assumed to be inside the internal network, then it is easy to tell whether communicating with a given IP address requires accessing some other network or not. Consider a network with 10 computers configured such that the computers have IP addresses ranging from 192.168.100.0 to 192.168.100.9. In practice, users can assign one or more Internet Protocol (IP) addresses to each MAC address, and set these IP addresses up in such a way that most network traffic occurs in small "pools" rather than across a wider group of machines. In practice, IP addresses are typically specified by a 32-bit value, and are commonly written as four groups of 3-digit decimal values (e.g. IP Addresses (IPv4)Ĭlearly, a different scheme of addressing is needed to enable computers to communicate with each other via Ethernet. Second, storing the address of every other computer on the planet on each machine would require a large amount of memory, and is not a good strategy due to the constant addition of new devices. First, with such a large shared connection packet collisions would occur frequently, causing communication to be unreliable. However, this is impractical for several reasons. If every computer in the world were connected to one large wire and knew every other computer's MAC address, then no further addressing schemes would be required. If multiple NICs are installed in one computer, they each have their own MAC addresses. Each network interface controller (NIC) in a computer has a unique medium access control (MAC) address. Each interface is continually listening for packets sent to its unique address.įigure 1. When Ethernet data is sent between two computers, it is sent in small pieces called "packets", and those packets contain the MAC address of the receiving interface. The MAC address or addresses for a specific Ethernet adapter are commonly printed on a label on the device itself, and are also accessible via operating system networking settings. MAC addresses consist of 48 bits, and are commonly expressed in groups of 2 hexadecimal digits (e.g.
Just like a home or business address must be specified in order to send a piece of postal mail, every port on every Ethernet adapter is assigned a unique address called a Medium Access Control (MAC) address by the manufacturer. If you are already familiar with these concepts or are not concerned about the "why" behind the recommendations in this paper, then you can skip to the Guidelines for Configuring Multi-NIC Systems section. This section explains how individual NICs are addressed, how packets are routed on Ethernet networks, and what a typical Ethernet packet transfer looks like.
Before explaining best practices for configuring controllers with multiple NICs, it is necessary to understand some basic concepts related to Ethernet networking.
0 kommentar(er)
