This is where you configure the DHCPv6 server, the DHCPv6 client and the DHCPv6 relay agent.
DHCPv6 server
Use the following buttons to access the tables and adjust the respective functions:
- DHCPv6 networks: This table is used to configure the basic settings of the DHCPv6 server, and to specify which interfaces they apply to.
- Interface name or relay: Name of the interface on which the DHCPv6 server is working, e.g. "INTRANET". Alternatively, you can also enter the IPv6 address of the remote DHCPv6 relay agent.
- DHCPv6 server activated: Activates or deactivates the entry.
- Rapid commit: With rapid commit activated, the DHCPv6 server responds directly to a solicit message with a reply message. Note: The client must explicitly include the rapid commit option in its solicit message.
- Primary DNS: IPv6 address of the primary DNS server.
- Secondary DNS: IPv6 address of the secondary DNS server.
- Import DNS search list from the internal DNS server: Indicates whether the DNS search list or the own domain for this logical network should be inserted from the internal DNS server, e.g., "internal". The own domain can be configured under . The default setting is "enabled".
- Import DNS search list from WAN: Specifies whether the DNS search list from the provider (e.g., provider-xy.com) is announced on this logical network. The default setting is "disabled".
- Address pool: Name of the address pool used for this interface. Note: If the DHCPv6 server operates 'stateful' addresses distribution, you must enter the corresponding addresses into the Address pools table.
- Prefix delegation pool: Name of prefix pools to be used by the DHCPv6 server. Note: If the DHCPv6 server is to delegate prefixes to other routers, you must enter the corresponding prefixes in the table Prefix delegation pools.
- Unicast address: By default the DHCPv6 server exclusively responds to multicast requests. If the DHCPv6 server should respond to a unicast request, this IPv6 address can be configured here. Generally speaking, multicast is sufficient for communication.
- Address pools: If distribution of the DHCPv6 server is to be stateful, this table defines an address pool:
- Address pool name: Name of the address pool
- First address: First address in the pool, e.g., "2001:db8::1"
- Last address: Last address in the pool, e.g., "2001:db8::9"
- Preferred lifetime: Here you specify the time in seconds that the client should treat this address as "preferred". After this time elapses, a client classifies this address as "deprecated".
- Valid lifetime: Here you specify the time in seconds that the client should treat this address as "valid".Note: If you use a prefix from a WAN interface for dynamic address formation, you cannot configure values for preferred lifetime and valid lifetime. In this case, the device automatically determines the values that apply to the prefix delegated by the provider.
- Receive prefix from: With this parameter you can assign addresses to the network clients from the prefix that the router retrieved from the WAN interface via DHCPv6 prefix delegation. Select the desired WAN interface here. For example, if the provider assigned the prefix "2001:db8::/64", you can then enter the value "::1" in the parameter First address and "::9" in Last address. In combination with the prefix "2001:db8::/64" as delegated by the provider, the clients receive addresses from the pool "2001:db8::1" to "2001:db8::9". If the provider prefix is greater than "/64", e.g., "/48" or "56", you must take subnetting for the logical network in to account in the address.
Example:
- Assigned provider prefix: "2001:db8:abcd:aa::/56"
- "/64" as the prefix of the logical network (subnet ID 1): "2001:db8:abcd:aa01::/64"
- First address: "0:0:0:0001::1"
- Last address: "0:0:0:0001::9"
Note: You should only use this mechanism if the provider assigns a fixed prefix. Otherwise, it is possible that the provider delegates a new prefix to the router, but the client still has an address from the pool with the old prefix. In this case, the client must update its address at the server.
- Prefix delegation pools: In this table, you specify the prefixes that the DHCPv6 server delegates to other routers:
- PD pool name: Name of the PD pool
- First prefix: First prefix to be delegated in the PD pool, e.g., "2001:db8:1100::"
- Last prefix: Last prefix to be delegated in the PD pool, e.g., "2001:db8:FF00::"
- Prefix length: Length of the prefixes in the PD pool, e.g., "56" or "60"
- Preferred lifetime: Here you specify the time in seconds that the client should treat this prefix as "preferred". After this time elapses, a client classifies this address as "deprecated".
- Valid lifetime: Here you specify the time in seconds that the client should treat this prefix as "valid".Note: If you use a prefix from a WAN interface for dynamic address formation, you cannot configure values for preferred lifetime and valid lifetime. In this case, the device automatically determines the values that apply to the prefix delegated by the provider.
- Receive prefix from: Name of the WAN interface from which the client should use the prefix to form the address or prefix.
- Reservations: If you want to assign fixed IPv6 addresses to clients, you can make a reservation for each client in this table:
- Interface name or relay: Name of the interfaces on which the DHCPv6 server is working, e.g., "INTRANET". Alternatively, you can also enter the IPv6 address of the remote relay agent.
- Address/PD-Prefix: IPv6 address, or PD prefix that you want to assign statically.
- Client ID: DHCPv6 unique identifier (DUID) of the client.DHCPv6 clients are no longer identified with their MAC addresses like DHCPv4 clients, they are identified with their DUID instead. The DUID can be read from the respective client, for example, on Windows with the shell command ipconfig /all or in WEBconfig under . For devices working as a DHCPv6 server, the client IDs for clients that are currently using retrieved IPv6 addresses are to be found under , and retrieved IPv6 prefixes are under . LANmonitor displays that client IDs under DHCPv6 server.
- Preferred lifetime: Here you specify the time in seconds that the client should treat this address as "preferred". After this time elapses, a client classifies this address as "deprecated".
- Valid lifetime: Here you specify the time in seconds that the client should treat this address as "valid".Note: If you use a prefix from a WAN interface for dynamic address formation, you cannot configure values for preferred lifetime and valid lifetime. In this case, the device automatically determines the values that apply to the prefix delegated by the provider.
- Receive prefix from: Name of the WAN interface from which the client should use the prefix to form the address or prefix.
DHCPv6 client
Use the following buttons to access the tables and adjust the respective functions:
- Interfaces: This table determines the behavior of the DHCPv6 client.
Note: Normally client behavior is controlled by the auto-configuration. Only make entries in this table if you want to use the client in "stand-alone" mode or if there are other specific options that deviate from the default settings.- Interface name: Name of the interface on which the DHCPv6 client is working. These can be LAN interfaces or WAN interfaces (remote stations), e.g. "INTRANET" or "INTERNET".
- Operating: Determines if and how the device enables the client. Possible values are:
- "Autoconfiguration": The device waits for router advertisements, and then starts the DHCPv6 client. This option is the default setting.
- "Yes": The device starts the DHCPv6 client as soon as the interface is active, without waiting for router advertisements. The device ignores the specifications from router advertisements.
- "No": The DHCPv6 client is disabled on this interface. Even if the device receives router advertisements, it will not start the client.
- Rapid commit: When rapid commit is activated, the client attempts to obtain an IPv6 address from the DHCPv6 server with just two messages. If the DHCPv6 server is configured correspondingly, it immediately responds to this solicit message with a reply message.
- Reconfigure accept: If the client successfully negotiates a re-configuration (reconfigure) with the server during first contact, the server can request the client to update its address or other information at any time. The mechanism is protected by the so-called 'Reconfigure Key', so that only the original server with the correct key can make requests to the client. If the client receives a reconfigure message without a valid reconfigure key, the client rejects this invocation.The client supports the "Reconfigure Key Authentication Protocol" according to RFC 3315 for the options "Renew" and "Information Request", and also "Rebind" as per RFC 6644. This option is enabled by default for WAN interfaces.
- Send own name (FQDN): The client sends its own host name (Fully Qualified Domain Name). By default, this option is active on LAN interfaces.
- Request DNS server: Specifies whether the client queries the DHCPv6 server for DNS servers. Note: You must enable this option in order for the device to obtain information about a DNS server.
- DNS search list: The client queries the DNS search list.
- Request address: Determines whether the client should request an IPv6 address from the DHCPv6 server. Note: Only activate this option if addresses configured by the DHCPv6 server via this interface are stateful, i. e. not distributed by 'SLAAC'.
- Request prefix: Determines whether the client should request an IPv6 prefix from the DHCPv6 server. Activating this option is only necessary if the device itself functions as a router and redistributes these prefixes. This option is enabled by default on WAN interfaces in order for the DHCPv6 client to request a prefix from the provider for use in its local network. This option is disabled by default on LAN interfaces because devices in a local network are more likely to function as clients rather than as routers.
DHCPv6 relay agent
Use the following buttons to access the tables and adjust the respective functions:
- Interfaces: A DHCPv6 relay agent forwards DHCP messages between DHCPv6 clients and DHCPv6 servers, which are located in different networks. This table determines the behavior of the DHCPv6 relay agent.
- Interface name: Name of the interface on which the relay agent receives requests from DHCPv6 clients, e.g. "INTRANET".
- DHCPv6-Relay-Agent-enabled: Determines if and how the device enables the relay agent. Possible values are:
- "Yes": Relay agent is enabled. This option is the default setting.
- "No": Relay agent is not enabled.
- Interface address: The relay agent's own IPv6 address on the interface that is configured under Interface name. This IPv6 address is used as a sender address in DHCP messages that are forwarded. This sender address enables DHCPv6 clients to uniquely identify a relay agent. An explicit specification of the interface address is necessary because an IPv6 host can have multiple IPv6 addresses for each interface.
- Destination address: The IPv6 address of the (destination) DHCPv6 server which the relay agent should forward DHCP requests to. The address can be either a unicast or link-local multicast address. When using a link-local multicast address, you must specify the destination interface where the DHCPv6 server is to be reached. All DHCPv6 servers and relay agents are available at the link-local multicast address ff02::1:2.
- Destination interface: The destination interface where the parent DHCPv6 server or the next relay agent can be reached. This information is essential if a link-local multicast address is configured under the destination address, as link local-multicast addresses are only valid at that respective link.