You are on page 1of 5

https://4sysops.

com/archives/the-difference-between-stateless-and-stateful-mode-of-a-windows-server-2008-r2-dhcpv6-server/

This article explains the difference between stateless and stateful mode of a
Windows Server 2008 R2 DHCP server for IPv6 (DHCPv6) and tells you how to
change this mode.

Michael Pietroforte

Michael Pietroforte is the founder and editor in chief of 4sysops. He has more than 35 years of experience in
IT management and system administration.

Contents of this article

 The difference between stateless and stateful IPv6 autoconfiguration


 Stateless mode and stateful mode of a Windows 2008 R2 DHCP server
 How to change a DHCPv6 server from stateless to stateful mode

When I first installed a DHCPv6 server on Window Server 2008 R2, my clients (Vista and Windows 7) were unable to
receive IP addresses. Thus, I started googling to find out what went wrong. I found quite a few official and unofficial
resources with promising advice. In the end, it turned out that most of those resources were either outdated or
simply provided wrong information. In my last post about DHCPv6 server installation, I mentioned the wrong advice
regarding client settings.

The difference between stateless and stateful IPv6 autoconfiguration

However, the most prominent confusion about setting up DHCPv6 on Windows Server 2008 R2 is the difference
between stateless and stateful autoconfiguration. I briefly discussed the difference already in my article about the
IPv6 features. With stateless autoconfiguration of IPv6 addresses, a host uses the IPv6 prefix (the subnet address)
advertised by a router on the link (subnet) to generate an IPv6 address.
Clients can use the MAC address of their network interface to determine the interface identifier. The interface
identifier is the last 64 bits of an IPv6 address. If you are interested in how this interface identifier generation works
in stateless autoconfiguration, I recommend this explanation (http://packetlife.net/blog/2008/aug/4/eui-64-ipv6/).

Stateful autoconfiguration is simply IP address assignment through a DHCPv6 server.


Stateless mode and stateful mode of a Windows 2008 R2 DHCP server

Much of the confusion on the web stems from the fact that when you install the DHCP role on a Window 2008 or R2
server, you have to choose whether you "Enable DHCPv6 stateless mode for this server" or "Disable DHCPv6 stateless
mode for this server" (see screenshots). Since disabling stateless mode seems to imply that you enable stateful
mode, many recommend that you re-install your DHCP server and make sure that your DHCP server is in stateful
mode because only then will it issue IPv6 addresses to DHCPv6 clients.

(Gran parte de la confusión en la web se debe al hecho de que cuando se instala la función DHCP en un servidor
Windows 2008 o R2, debe elegir si "Habilitar el modo sin estado DHCPv6 para este servidor" o "Deshabilitar el modo
sin estado DHCPv6 para este servidor "(ver capturas de pantalla). Dado que deshabilitar el modo sin estado parece
implicar que habilita el modo con estado, muchos recomiendan que reinstale su servidor DHCP y asegurarse de que
su servidor DHCP esté en modo con estado (stateful) porque solo entonces emitirá direcciones IPv6 a los clientes
DHCPv6.)
This claim is wrong. As to my tests, this setting makes no difference with regard to automatic IPv6 address
assignment through a Windows DHCPv6 server. The only difference between those two options is that if you choose
to enable stateless mode, the installation wizard will ask for a Parent Domain and an IPv6 DNS Server. The reason for
this is that, with stateless autoconfiguration, clients can only receive the IPv6 prefix from a router to derive the IPv6
address but no additional network settings as the DNS server.

However, a router can tell clients to obtain this configuration from a DHCPv6 server by setting the so-called M Flag
to 0 and the O Flag to 1. In this scenario, the corresponding DHCP server runs in stateless mode because it won't
assign IPv6 addresses to clients. But since you have no IPv6 scopes in stateless mode on the DHCP server where you
could assign those options, you have to configure them during the DHCP server installation and assign them to the
server. More information about the M Flag and O Flag can be found in this article (http://technet.microsoft.com/hi-
in/magazine/2007.03.cableguy(en-us).aspx).

(Esta afirmación está mal. En cuanto a mis pruebas, esta configuración no hace ninguna diferencia con respecto a la
asignación automática de direcciones IPv6 a través de un servidor DHCPv6 de Windows. La única diferencia entre
esas dos opciones es que si elige habilitar el modo sin estado, el asistente de instalación le pedirá un Dominio
principal y un Servidor DNS IPv6. La razón de esto es que, con la configuración automática sin estado, los clientes solo
pueden recibir el prefijo IPv6 de un enrutador para derivar la dirección IPv6 pero no configuraciones de red
adicionales como el servidor DNS.

Sin embargo, un enrutador puede decirles a los clientes que obtengan esta configuración de un servidor DHCPv6
configurando el denominado Indicador M en 0 y el Indicador O en 1. En este escenario, el servidor DHCP
correspondiente se ejecuta en modo sin estado porque no se asignará Direcciones IPv6 a clientes. Pero como no tiene
ámbitos IPv6 en modo sin estado en el servidor DHCP donde podría asignar esas opciones, debe configurarlas
durante la instalación del servidor DHCP y asignarlas al servidor. Puede encontrar más información sobre la bandera
M y la bandera O en este artículo.( (http://technet.microsoft.com/hi-in/magazine/2007.03.cableguy(en-us).aspx))
How to change a DHCPv6 server from stateless to stateful mode
I also often saw the question of how to change the mode of a Windows DHCPv6 server from stateless to stateful
mode. Since there is no explicit setting where you could change a Windows DHCP server from stateful to stateless
mode in the DHCP management console, it is often recommended to re-install the DHCP server. However, from what
I have just said above, it is clear that this advice doesn't make sense.

All you have to do is to change the DHCP server from stateless to stateful mode is to add and activate an IPv6 scope
and you get a stateful DHCPv6 server that is able to assign IPv6 addresses to clients.

También a menudo vi la cuestión de cómo cambiar el modo de un servidor DHCPv6 de Windows de modo sin estado a
estado. Como no hay una configuración explícita en la que pueda cambiar un servidor DHCP de Windows del modo
con estado a sin estado en la consola de administración de DHCP, a menudo se recomienda volver a instalar el
servidor DHCP. Sin embargo, por lo que acabo de decir anteriormente, está claro que este consejo no tiene sentido.

Todo lo que tiene que hacer es cambiar el servidor DHCP del modo sin estado al modo con estado es agregar y activar
un alcance IPv6 y obtendrá un servidor DHCPv6 con estado que puede asignar direcciones IPv6 a los clientes.
And if you want to move a DHCP server from stateful to stateless mode, you simply have to deactivate or delete all
IPv6 scopes from the server.

The parameters Parent Domain and IPv6 DNS Server, which the installation wizard asked for during the DHCP server
role installation if you chose "enable stateless mode," can be added manually to the Server Options node in the
DHCP management console. The stateless DHPC server can then configure clients with these settings while the IPv6
prefix has to be provided by a router.

Y si desea mover un servidor DHCP del modo con estado a sin estado, simplemente tiene que desactivar o eliminar
todos los ámbitos IPv6 del servidor.

Los parámetros Dominio principal y Servidor DNS IPv6, que solicitó el asistente de instalación durante la instalación
del rol del servidor DHCP si elige "habilitar el modo sin estado", se pueden agregar manualmente al nodo Opciones
del servidor en la consola de administración de DHCP. El servidor DHPC sin estado puede configurar a los clientes con
estas configuraciones mientras que el enrutador debe proporcionar el prefijo IPv6.

RESUMIENDO: The difference between stateless and stateful IPv6 autoconfiguration


Stateless (=Enable ...stateless mode) - clients generate addresses by assistance from a router (this is configurable)
Stateful (=Disable ...stateless mode) - dhcp server assigns ip addresses to clients

Fuente:
https://4sysops.com/archives/the-difference-between-stateless-and-stateful-mode-of-a-windows-server-2008-r2-
dhcpv6-server/
https://4sysops.com/archives/how-to-install-a-dhcp-server-for-ipv6-dhcpv6-on-windows-server-2008-r2/

Adaptado por jdp/ASO /

You might also like