12 Advanced TCPIP Configuration
12 Advanced TCPIP Configuration
The current IP addressing standard, version 4, will eventually run out of unique addresses, so a new
system is being developed. It is named IP version 6 or IPv6. You should know about the following IPv6
features:
Feature Description
The Internet Corporation for Assigned Names and Numbers (ICANN)
assigns IPv6 addresses based on the following strategy:
The IPv6 address is a 128-bit binary number. A sample IPv6 IP address looks like:
35BC:FA77:4898:DAFC:200C:FBBC:A007:8973. The following list describes the features of an IPv6
address:
The 64-bit prefix can be divided into various parts, with each part having a specific meaning.
The prefix length identifies the number of bits in the relevant portion of the prefix. To indicate
the prefix length, add a slash (/) followed by the prefix length number.
Bits past the end of the prefix length are all binary 0s. For example, the full 64-bit prefix for
address 2001:0DB8:4898:DAFC:200C:FBBC:A007:8973 is
2001:0DB8:4898:DAFC:0000:0000:0000:0000/64.
Full quartets with trailing 0's in the prefix address can be omitted (for example
2001:0DB8:4898:DAFC::/64).
If the prefix is not on a quartet boundary (this applies to any prefix that is not a multiple of 16),
any hex values listed after the boundary should written as 0's. For example, the prefix
2001:0DB8:4898:DAFC::/56 should be written as 35BC:FA77:4898:DA00::/56. Remember,
only leading 0's within a quartet can be omitted.
Be aware that the prefix length number is a binary value, while the prefix itself is a
hexadecimal value.
Global routing information is identified within the 64-bit prefix by subdividing the prefix using varying
prefix lengths. The following graphic is an example of how the IPv6 prefix could be divided:
This sample assignment of IPv6 addresses is explained in the following table:
Prefix Description
The Internet Corporation for Assigned Names and Numbers (ICANN) is responsible for
the assignment of IPv6 addresses. ICANN assigns a range of IP addresses to Regional
Internet Registry (RIR) organizations. Each current regional organization corresponds
roughly to a continent.
Regional
Internet
Registry The exact size of the address range assigned to the RIR may vary, but current
(RIR) guidelines assign a minimum prefix of 12-bits. In the above example, the RIR has been
assigned a 12-bit prefix, and is responsible for addresses in the following range:
2000::/12 to 200F:FFFF:FFFF:FFFF::/64
A regional organization subdivides its block of IP addresses into smaller blocks and
assigns those blocks to National Internet Registries (NIR), Local Internet Registries
(LIR), or Internet Service Providers (ISP). Larger organizations can further subdivide the
address space to allocate to smaller ISPs.
Internet
Service The exact size of the address range assigned by the RIR may vary, but current
Provider guidelines assign a minimum prefix of 32-bits. In the above example, the ISP has been
(ISP) assigned a 32-bit prefix, and is therefore responsible for addresses in the following
range:
2001:0DB8::/32 to 2001:0DB8:FFFF:FFFF::/64
Although the exact size of the address range assigned to a site may vary, by
Site convention, each site is assigned a 48-bit site ID. In the above example, the site is
responsible for managing the addresses in the following range:
2001:0DB8:4898::/48 to 2001:0DB8:4898:FFFF::/64
ISPs typically follow these guidelines for assigning address ranges to sites:
By default, all sites that represent a network, including home networks, get an
address with a 48-bit prefix.
Sites that require an address space larger than this might be assigned two
consecutive blocks, or might be allocated an address with a 47-bit prefix.
If the network is known to have only a single subnet, the ISP might assign a 64-
bit prefix. This is typically used for mobile devices.
If the network is known to have only a single device, such as a dialup
connection, the ISP might assign a 128-bit prefix.
Most networks receive an address range identified with a 48-bit prefix. The remaining
16-bits in the global routing prefix are then used by the local network administrator for
creating subnets. In the example above, the site has received the prefix of
2001:0DB8:4898::/48. The following list shows some of the subnets that could be
created by the administrator using a 64-bit prefix:
2001:0DB8:4898:0001::/64
Subnet ID
2001:0DB8:4898:0002::/64
2001:0DB8:4898:0003::/64
...
2001:0DB8:4898:FFFD::/64
2001:0DB8:4898:FFFE::/64
2001:0DB8:4898:FFFF::/64
In most cases, individual interface IDs are not assigned by ISPs, but are rather generated
automatically or managed by site administrators. Interface IDs must be unique within a subnet, but can
be the same if the interface is on different subnets. All addresses that identify a single interface,
except those that start with 000 binary, but use a 64-bit interface ID that follows the modified EUI-64
format. On Ethernet networks, the modified EUI-64 format interface ID can be automatically derived
from the MAC address using the following process:
In this example, the MAC address of 20-0C-FB-BC-A0-07 in modified EUI-64 format becomes:
220C:FBFF:FEBC:A007 (portions in red indicate modified values).
IPv6 Address Types
In IPv6, addresses are assigned to interfaces (network connections). All interfaces are required to
have some addresses, and interfaces can have more than one address. IPv6 identifies the following
types of addresses:
Address
Description
Type
Unicast addresses are assigned to a single interface for the purpose of allowing that one
host to send and receive data. Packets sent to a unicast address are delivered to the
interface identified by that address.
Unique local addresses are private addresses used for communication within a
site or between a limited number of sites.
FF02::1 is for all nodes on the local link. This is the equivalent of the IPv4 subnet
broadcast address. FF01::1 is for all interfaces on a node.
FF02::2 is for all routers on the local link. FF01::1 is for all routers on the node.
FF02::1:2 is for all DHCP servers or DHCP relay agents on the local link. DHCP
relay agents forward these packets to other subnets.
The anycast address is a unicast address that is assigned to more than one interface,
typically belonging to different hosts. An anycast packet is routed to the nearest interface
having that address (based on routing protocol decisions).
The local loopback address for the local host is 0:0:0:0:0:0:0:1 (also identified as ::1 or
Loopback ::1/128). The local loopback address is not assigned to an interface. It can be used to
verify that the TCP/IP protocol stack has been properly installed on the host.
The unspecified address is 0:0:0:0:0:0:0:0 (also identifies as :: or ::/128). The unspecified
address is used when there is no IPv6 address. It is typically used during system startup
Unspecified
when the host has not yet configured its address. The unspecified address should not be
assigned to an interface.
Note: There are no broadcast addresses in IPv6. IPv6 multicast addresses are used instead of
broadcast addresses.
Method Description
Static full Static full assignment is where the entire 128-bit IPv6 address and all other
assignment configuration information is statically assigned to the host.
Static partial Static partial assignment is where the prefix is statically assigned and the
assignment interface ID uses the modified EUI-64 format derived from the MAC address.
Stateless autoconfiguration is where clients automatically generate the interface
Stateless ID, and learn the subnet prefix and default gateway through the Neighbor
autoconfiguration Discovery Protocol (NDP). NDP uses the following messages for
autoconfiguration:
Router solicitation (RS) is a message sent by the client to request that
routers respond.
Router advertisement (RA) is a message sent by the router periodically
and in response to RS messages to inform clients of the IPv6 subnet
prefix and the default gateway address.
NDP is also used by hosts to discover the address of other interfaces on the
network, replacing the need for Address Resolution Protocol (ARP).
Note: Even though NDP provides enough information for the addressing of the
client and for clients to learn the addresses of other clients on the network, it does
not provide the client with DNS server information or other IP configuration
information besides the IP address and the default gateway.
IPv6 uses an updated version of DHCP (called DHCPv6) that operates in one of
two different modes:
Stateful DHCPv6 is when the DHCP server provides each client with the
IP address, default gateway, and other IP configuration information (such
as the DNS server IP address). The DHCP server tracks the status (or
DHCPv6
state) of the client.
Stateless DHCPv6 does not provide the client an IP address and does
not track the status of each client, but rather is used to supply the client
with the DNS server IP address. Stateless DHCPv6 is most useful when
used in conjunction with stateless autoconfiguration.
When a host starts up, it uses the following process to configure the IPv6 address for each interface:
1. The host generates an IPv6 address using the link-local prefix (FE80::/10) and modifying the
MAC address to get the interface ID. For example, if the MAC address is 20-0C-FB-BC-A0-07,
the link-local address for the interface would be: FE80::220C:FBFF:FEBC:A007.
2. The host then sends a neighbor solicitation (NS) message addressed to its own link-local
address to see if the address it has chosen is already in use.
o If the address is in use, the other network host responds with a neighbor
advertisement (NA) message. The process stops and manual configuration of the host
is required.
o If the address is not in use (no NA message), the process continues.
3. The host waits for a router advertisement (RA) message from a router to learn the prefix.
o If an RA message is not received, the host sends out a router solicitation (RS)
message addressed to all routers on the subnet using the multicast address FF02::2.
o The router sends out an RA message addressed to all interfaces on the subnet using
the multicast address FF02::1.
o If no routers respond, the host attempts to use stateful DHCPv6 to receive
configuration information.
4. The RA message contains information that identifies how the IPv6 address and other
information is to be configured. Possible combinations are:
Configuration
Description
Method
Obtain the interface ID, subnet prefix, default gateway, and other
configuration information from a DHCPv6 server.
Use stateful
The host sends out a REQUEST message addressed to the multicast
autoconfiguration
address FF02::1:2 to request this information from the DHCPv6
server.
Use stateless Set the interface ID automatically.
autoconfiguration Get the subnet prefix and default gateway from the RA message.
Get DNS and other configuration information from a DHCPv6 server.
The host sends out an INFORMATION-REQUEST message
addressed to the multicast address FF02::1:2 to request this
information from the DHCPv6 server.
The worldwide implementation from IPv4 to IPv6 will be a long process. Although not yet widely
adopted, you can implement IPv6 if your systems support it. As the implementation of IPv6 proceeds,
there will be cases when compatibility with IPv4 is required. The following table lists various strategies
for deploying IPv6:
Method Description
With a dual stack configuration, both the IPv4 and IPv6 protocol stacks run
concurrently on a host. IPv4 is used to communicate with IPv4 hosts, and IPv6
is used to communicate with IPv6 hosts. When implemented on hosts,
Dual stack intermediate routers and switches must also run both protocol stacks.
Use a dual stack configuration to enable a host to communicate with both IPv4
and IPv6 hosts.
Tunneling wraps an IPv6 packet within an IPv4 packet, allowing IPv6 hosts or
sites to communicate over the existing IPv4 infrastructure. With tunneling, a
device encapsulates IPv6 packets in IPv4 packets for transmission across an
IPv4 network, and then the packets are de-encapsulated to their original IPv6
packets by another device at the other end.