| By Richard Petersen | Article Rating: |
|
| December 27, 2005 10:00 PM EST | Reads: |
28,617 |
IPv6 can be used to automatically connect a host to a network using stateless auto-configuration, doing away with the need for any IP addressing support like a DHCP server.
In an IPv6 network, the IPv6 protocol includes information that can directly configure a host. With IPv4 you either have to manually configure each host or rely on a DHCP server to provide configuration information. With IPv6, configuration information is integrated into the Internet protocol directly. IPv6 autoconfiguration capabilities are known as stateless, meaning that it can directly configure a host without the recourse to an external server. Alternatively, DHCP is stateful, where the host relies on an external DHCP server to provide configuration information. Stateless autoconfiguration has the advantage of hosts not having to rely on a DHCP server to maintain connections to a network. Networks could even become mobile, hooking into one subnet or another, automatically generating addresses as needed. Hosts are no longer tied to a particular DHCP server. Many ISPs still use the IPv4 protocol and to use IPv6 with these networks requires special services such as 4to6. This is beyond the scope of this article.
IPv6 Addressing
IPv6 introduces major changes into the format and method of addressing systems under the Internet Protocol. There are several different kinds of addressing with different fields for the network segment. The host segment has been expanded to a 64-bit address, allowing direct addressing for a far larger number of systems. Each address begins with a type field specifying the kind of address, which will then determine how its network segment is organized. These changes are designed not only to expand the address space but to also provide greater control over transmissions at the address level.
An IPv6 address consists of 128 bits, up from the 32 bits used in IPv4 addresses. The first 64 bits are used for network addressing, of which the first few bits are reserved for indicating the address type. The last 64 bits are used for the interface address, known as the interface identifier field. An IPv6 address is written as eight segments representing 16 bits each (128 bits total). To more easily represent 16-bit binary numbers, hexadecimal numbers are used.
In IPv6, addressing is controlled by the format prefix in the network part of the address that operates as a kind of address type. The format prefix is the first field of the IP address. The three kinds of single destination network addresses are global, link-local, and site-local. Global addresses can be sent across the Internet and have a format prefix that begins with 3. Link-local addresses are used for physically connected systems on a local network and use the format prefix FE80. Site-local can be used for any hosts on a private network and use the format prefix FEC0. Site-local addresses operate similar to IPv4 private addresses.
In the following example the first four segments represent the network part of the IPv6 site-local address, and the following four segments represent the interface (host) address:
FEC0:0000:0000:0000:0008:0800:200C:417A
Segments with all zeros can be reduced to a single zero.
FEC0:0:0:0:8:800:200C:417A
Sequences of zeros can use a shorthand symbol consisting of a double colon (::).
FEC0::8:800:200C:417A
The identifier part of the IPv6 address takes up the second 64 bits, consisting of four segments containing four hexadecimal numbers. This is the address used to identify the host. The interface ID is a 64-bit (four-segment) Extended Unique Identifier (EUI-64) generated from a network device's Media Access Control (MAC) address. There are security concerns that the identifier based directly on a constant MAC address could be used to track a host. As an alternative, a method of generating randomized and temporary identifiers has been proposed.
Generating the Link-Local Address for Local Networks
To auto-configure hosts on a local network, IPv6 makes use of each network device's hardware MAC address. This address is used to generate a temporary address with which the host can be queried and configured. Be sure that IPv6 addressing is first enabled on your host's network device. This is an option in the device's General panel in the system-config-network on Fedora Core 4.
The MAC address is used to create a link-local address, one with a link-local prefix, FE80::0, followed by an interface identifier. The link-local prefix is used for physically connected hosts such as those on a small local network.
A uniqueness test is then performed on the generated address. Using the Neighbor Discovery Protocol (NDP), other hosts on the network are checked to see if another host is already using the generated link-local address. If no other host is using the address, the address is assigned for that local network. At this point the host has only a local address that's valid within the local physical network. Link-local addresses cannot be routed to a larger network.
Generating the Full Address: Router Advertisements
Once the link-local address has been determined, the router for the network is then queried for additional configuration information. In the case of stateless addresses, the router provides the network address, such as the network's Internet address. This address is then added to the local address, replacing the original link-local prefix, giving either a complete global Internet address or, in the case of private networks, site-local addresses. Routers will routinely advertise this address information, though it can also be specifically requested. The NDP protocol is used to query and send the information using ICMPv6 packets. Before the address is officially assigned, a duplicate address detection procedure checks to see if the address is already in use. The process depends on the router's providing the appropriate addressing information in the form of router advertisements.
Figure 1 shows a network that is configured with stateless address autoconfiguration. First, each host determines its interface identifier using its own MAC hardware address. This is used to create a temporary link-local address for each host using the FE08::0 prefix. This allows initial communication with the network's router. The router then uses its network prefix to create full Internet addresses, replacing the link-local prefix.
Addressing for Private Networks
In a private network, your router would use a site-local address for the network prefix, such as FEC0::0. This network prefix would then be combined with the host's identifier to generate a full IPv6 private address (see Figure 2). In a private network, the address of the first host as shown in Figure 2 is:
FEC0:0:0:0:FEDC:BA98:7654:3210
Router Renumbering
With IPv6, routers have the ability to renumber the addresses on their networks by changing the network prefix. Renumbering is carried out through the Router Renumbering Protocol, RR. Renumbering is often used when a network changes ISP providers, requiring that the network address for all hosts be changed (see Figure 3). It can also be used for mobile networks where a network can be plugged into different larger networks, renumbering each time.
With renumbering, routers place a time limit on addresses, similar to the lease time in DHCP, by specifying an expiration limit for the network prefix when the address is generated. To ease transition, interfaces still keep their old addresses as deprecated addresses, while the new ones are first being used. The new ones will be the preferred addresses used for any new connections while deprecated ones are used for older connections. In effect a host could have two addresses, one deprecated and one preferred. This regeneration of addresses effectively renumbers the hosts.
Linux As a IPv6 router: radvd
A Linux system that operates as a router uses the radvd Router Advertisement Daemon to advertise addresses, specifying a network prefix in the /etc/radvd.conf file. The radvd daemon will detect router network address requests from hosts, known as router solicitations, and provide them with a network address using a router advertisement. These router advertisements will also be broadcast to provide the network address to those hosts that do not send in requests. For radvd to work you will have to turn on IPv6 forwarding. Use sysctl and set net.ipv6.conf.all.forwarding to 1. To start up the radvd daemon, use the radvd start-up script. To check the router addresses radvd is sending, you can use radvdump.
You will have to configure the radvd daemon yourself, specifying the network address to broadcast. Configuration though is very simple as the full address will be automatically generated using the host's hardware address. A configuration consists of interface entries that in turn list interface options, prefix definitions and options, along with router definitions if needed. The configuration is placed in the /etc/radvd.conf file, which would look something like this:
This assumes one interface is used for the local network, eth0. This interface configuration lists an interface option (AdvSendAdvert) and a prefix definition along with two prefix options (AdvOnLink and AdvAutonomous). To specify prefix options for a specific prefix, add them within parentheses following the prefix definition. The prefix definition specifies your IPv6 network address. If a local area network has its own network address, you will need to provide its IPv6 network prefix address. For a private network, like a home network, you can use the silte-local IPv6 prefix that operates like the IPv4 private network addresses, 192.168.0. The above example uses a site-local address that is used for private IPv6 networks, fec0:0:0:0::, which has a length of 64 bits.
interface eth0 {
AdvSendAdvert on;
prefix fec0:0:0:0::/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
The AdvSendAdvert interface option turns on network address advertising to the hosts. The AdvAutonomous network prefix option provides automatic address configuration, and AdvOnLink simply means that host requests can be received on the specified network interface.
A second network interface is then used to connect the Linux system to an ISP or larger network. If the ISP supports IPv6, this is simply a matter of sending a router solicitation to the ISP router. This would automatically generate your Internet address using the hardware address of the network interface used to connect to the Internet and the ISP router's advertised network address. In Figure 2, a local network, eth0 network interface, connects to the local network, whereas eth1 connects to the Internet.
Conclusion
Stateless IPv6 autoconfiguration requires no independent server or source to connect to a network. It is a direct plug-and-play operation, where the hardware network interfaces and routers can directly determine the correct addresses. DCHP, currently in wide use, is an older method that requires a separate server to manage and assign all addresses. Should the DHCP server ever fail, hosts could not connect. With the IPv6 protocol in place, your address is automatically generated using your network hardware MAC interface and the ISP router's network address. Home networks can use the same structure to automatically connect any network device to your router. No local DHCP server has to be maintained. To use a Linux system as an IPv6 router, you configure and run the radvd daemon. This daemon uses a very simple configuration to automatically configure the IPv6 network addresses for your local hosts.
References
- Check the RFCs at www.ietf.org/rfc
RFC 3513: Internet Protocol Version 6 (IPv6) Addressing Architecture
RFC 2894: Router Renumbering for IPv6
RFC 2461: Neighbor Discovery for IP Version 6 (IPv6)
RFC 2462:IPv6 Stateless Address Autoconfiguration
RFC 1897: IPv6 Testing Address Allocation
RFC 3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6 - Linux IPv6 Router Advertisement daemon: http://v6web.litech.org/radvd/
- Linux IPv6 HOWTO: www.tldp.org/HOWTO/Linux+IPv6-HOWTO/
- Linux IPv6 FAQ: www.linuxhq.com/IPv6/
- IPv6 information: www.ipv6.org
Published December 27, 2005 Reads 28,617
Copyright © 2005 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
About Richard Petersen
Richard Petersen holds a M.L.I.S. in Library and Information Studies. He
currently teaches Unix and C/C++ courses at the University of California, Berkeley.
![]() |
Ned 09/06/07 12:08:53 PM EDT | |||
Your stupid popup ads render your site worthless; I will not come back. |
||||
![]() |
news desk 12/27/05 11:11:19 PM EST | |||
IPv6 can be used to automatically connect a host to a network using stateless auto-configuration, doing away with the need for any IP addressing support like a DHCP server. In an IPv6 network, the IPv6 protocol includes information that can directly configure a host. |
||||
![]() |
news desk 12/27/05 10:58:59 PM EST | |||
IPv6 can be used to automatically connect a host to a network using stateless auto-configuration, doing away with the need for any IP addressing support like a DHCP server. In an IPv6 network, the IPv6 protocol includes information that can directly configure a host. |
||||
- Ulitzer’s Amazing First 30 Days in Public Beta
- Why an Application Grid?
- Will Ulitzer Dominate News Content on The Web? -Gartner
- Building Private and Hybrid Clouds with Ubuntu 9.04
- Ulitzer Responds to Published Reports
- Ubuntu-based Open Source Linux Mint Tests KDE Version
- Is Cloud Computing Like Teenage Sex?
- Sun Upgrades VirtualBox
- Should Developers Care About Cloud Computing?
- Ted Weissman and Lois Paul & Partners PR Firm
- How to Rebuild a Home Network Integrating Ubuntu and Mac OS X
- Ulitzer’s Amazing First 30 Days in Public Beta
- Initial Thoughts on IBM Acquisition of Sun Microsystems
- Amazon Fiddles with Utility Pricing
- Why an Application Grid?
- Will Ulitzer Dominate News Content on The Web? -Gartner
- Micro Focus Offers Micro Focus COBOL for Eclipse
- Sun CEO Jonathan Schwartz Scopes Out Future for Sun's Cloud
- Building Private and Hybrid Clouds with Ubuntu 9.04
- SCO Files Reorg Plan
- The i-Technology Right Stuff
- Linux.SYS-CON.com Exclusive: Linus Discloses *Real* Fathers of Linux
- After Ubuntu, Windows Looks Increasingly Bad, Increasingly Archaic, Increasingly Unfriendly
- Linus' Top Ten SCO Barbs
- Netscape Co-Founder's 12 Reasons for Growth of Open Source
- A Closer Look at Damn Small Linux
- Introducing "Cooperative Linux" - Linux for Windows, No Less
- *POINT - COUNTERPOINT SPECIAL* What's Wrong with the Open Source Community?
- Linux.SYS-CON.com Exclusive: What Would UserLinux Look Like?
- i-Technology Viewpoint: The New Paradigm of IT Buying






































