Last adaptation to the version: 14.1.0 (08.2025)
- Das Design des Dialogs wurde überarbeitet
- Set a extc-Variables with more than 1000 required leases
Define IPv6 address on interface
UTMuser@firewall.name.fqdnNetworkNetwork configuration 
Schnittstelle IP-Adresse hinzufügen
First, an IPv6 address with subnet and the corresponding zones must be entered on the interface on which IPv6 is to be "spoken". This IP determines the range in which the DHCP pool is located:
Configuration at menu / edit Interfaces / Tab IP Addresses
An IP address can be entered directly in the click box, in this example »2001:DB8::1/64.
DHCPv6
The DHCPv6 address pool setup is only slightly different from the DHCP setup with IPv4.
Basic knowledge of IPv6 can be found here.
General
| Caption | Value | Description | UTMuser@firewall.name.fqdnNetwork  Configured DHCPv6 pool
|
|---|---|---|---|
| Enable detailed logging: | Off | When activated, all DHCP requests are recorded in the syslog. | |
DHCP-Pools DHCP-Pools | |||
| Multiple DHCP pools can be added. After clicking , the setup wizard opens and the DHCP parameters can be specified. | |||
| Ignore other SDHCP-Servers: | Off | When activated, other DHCP servers (IPv4 and IPv6) are ignored. | |
If more than 1000 IP addresses (across all pools together) are required via DHCP, the number of possible leases must be increased. This is done in the menu Area Extc Variables with the variable MAXLEASES. The value 0 corresponds to the default value of the service: 1000 leases. | |||
In step 1, a unique name for the pool as well as the start and end address must be specified.
The name is freely selectable, the pool start and end addresses are addresses from the previously defined subnet.
Finish the setup with the button
Edit pool
Once the pool has been created correctly, it can be edited with .
General |
UTMuser@firewall.name.fqdnNetworkNetwork configuration  Edit pool - general
| |||
| Changes to the pool range start and pool range end possible | ||||
Options - DHCP Optionen | ||||
| Option | Option number | Value | Description |  |
|---|---|---|---|---|
| Router: | 3 | »2001:db8::1 | Router as configured in Define IPv6 address on interface. | |
| Domain name: | 15 | securepoint.local | Name of the domain in which the DHCP leases are assigned | |
| Name server: | 5 | »2001:db8::1 | Name server as configured in step 2 | |
| Netbios Nameserver: | 44 | NetBIOS over TCP/IP Name Server Option | ||
| SMTP-Server: | 69 | Simple Mail Transport Protocol (SMTP) Server Option | ||
| NTP Server: | 41 | Servers should be listed in order of preference. | ||
| Vendor Encapsulated Options: | 43 | Values must be given coded. | ||
| TFTP Server Name: | 66 | profile.gigaset.net | The IPv6 address, or hostname from the TFTP server option tftp-server-name text; | |
| Bootfile Name: | 67 | The name of the bootfile file option bootfile-name text; | ||
| Default URL: | 114 | https://teamwork.gigaset.com/gigawiki/display/GPPPO/DHCP+option+114 | Default URL option default-url string; | |
| VLAN ID: | 132 | The ID of the VLAN used option vlan-id code 132 = text; option vlan-id "128"; | ||
| Next Server: | The IPv6 address of the Next server | |||
| Default Lease Time: | 51 | 600 Seconds | Default validity period of the IP address if the client has not requested an explicit duration. | |
| Maximal Lease Time: | 7200 Seconds | Maximum validity period of the IP address in seconds that the client may receive when explicitly requested. | ||
| Reject unknown clients: | No | If activated Yes, an IP address is only assigned if there is a entry at Static DHCP tab for the MAC address of the client. notempty Changed standard behaviour ab v12.7: The static lease entry for the DHCP must be in the same pool to be considered known. The static lease entry for the DHCP must be in the same pool to be considered known. | ||
Static DHCP
If hosts are to be assigned predefined IP addresses ( fixed IPs bound to the MAC address, but assigned by the UTM), these IPs can be reserved with static leases:
Configuration under Area Static DHCP button
| Host: | Hostname | Meaningful host name | UTMuser@firewall.name.fqdnNetworkNetwork configuration  Dialogue Add lease
|
| Ethernet: | 00:00:00:00:00:00 | MAC address of the host | |
| IP: | IP address to be reserved exclusively for this host | ||
| Save and close | Saves and takes over the lease | ||
|
notempty Important: Leases must necessarily be in an existing DHCP pool! |
UTMuser@firewall.name.fqdnNetwork  Overview static DHCP leases
| ||
|
notempty Joint use of static and dynamic IP addresses within a pool is possible. | |||
Static leases outside a pool
| Existing static leases that are not within a DHCP pool must be changed! If such leases are detected after an update, a message is displayed prompting to adjust the DHCP settings.
|
 | ||
Configuration of DHCP-Relay
With the DHCP relay, devices can receive their network configuration dynamically via the network, even if the DHCP server is located in another subnet.
| Caption | Value | Description | UTMuser@firewall.name.fqdnNetwork  Network configuration DHCP relay overview
|
|---|---|---|---|
| activate Debug mode: notempty New as of v12.7.1 |
Off | Log messages are only written when activated On | |
DHCP Relay IPv4 DHCP Relay IPv4 | |||
| DHCP server IP addresses:notempty updated |
»192.168.178.1 | IP addresses of the DHCP server/s The network/s in which the servers are located must be known to the UTM. | |
| DHCP-Relay Client Side Interfaces: | LAN2 | Interfaces for which the DHCP server is to be responsible. | |
DHCP Relay IPv6 DHCP Relay IPv6 | |||
| DHCP-Relay Server Side Interfaces: | LAN1 | Interface behind which a DHCP-v6 server is located. | |
| DHCP-Relay Client Side Interfaces: | LAN2 | Interfaces for which a DHCP-v6 server is to be responsible. | |
Widget
In the administrator interface of the UTM, there is a DHCP widget that provides an overview of the existing DHCP connections.
Further information can be found in the Wiki article UTM Widgets.