Aller à :navigation, rechercher
Wiki

DHCP-Server IPv6

De Securepoint Wiki





























In dieser Seite werden die Variablen für unterschiedliche Sprachen definiert.
Diese Seite wird auf folgenden Seiten eingebunden




















{{var | Andere DHCP-Server ignorieren










































Setting up a DHCPv6 address pool

Last adaptation to the version: 14.1.0 (08.2025)

New:
  • The dialog design has been revised
Last updated: 
notempty
This article refers to a Beta version
Access: UTM-IP:Port or UTM-URL:Port
Port as configured at Network / Appliance Settings / Webserver
Default-Port: 11115
i.e.: https://utm.ttt-point.de:11115
Default: https://192.168.175.1:11115 Network Network Configuration


Define IPv6 address on interface

Edit Ethernet interface UTMuser@firewall.name.fqdn Network Network 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 → Network →Network Configuration / edit Interfaces / Tab IP Addresses
An IP address can be entered directly in the click box, in this example »2001:DB8::1/64.


The DHCPv6 address pool setup is only slightly different from the DHCP setup with IPv4.
Basic knowledge of IPv6 can be found here.


DHCP

General

General
Caption Value Description Network configuration UTMuser@firewall.name.fqdn Network
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 Add Pool, 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 Extras Advanced Settings Area Extc Variables with the variable MAXLEASES.

The value 0 corresponds to the default value of the service: 1000 leases.

If more leases are required, the actual value must be entered here. Edit
Add pool UTMuser@firewall.name.fqdnNetworkNetwork configuration
The DHCPv6 address pool for this subnet is set up under Network Network configuration Area DHCP pools button Add pool.
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.
Add pool UTMuser@firewall.name.fqdnNetworkNetwork configuration
In step 2, enter the IPv6 address of the name server. In this example the UTM: 2001:DB8::1/---
Add pool UTMuser@firewall.name.fqdnNetworkNetwork configuration
In step 3, Router Advertisement On must be enabled.

Finish the setup with the button Finish
Edit pool

Once the pool has been created correctly, it can be edited with .

General
Edit pool UTMuser@firewall.name.fqdn Network Network 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
  • If the value is missing, TFTP may not work.
    • 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

    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 Network Network Configuration Area Static DHCP button Add Lease

    Host: Hostname Meaningful host name Add lease UTMuser@firewall.name.fqdn Network Network configuration
    Dialogue Add lease
    Ethernet: 00:00:00:00:00:00 MAC address of the host
    IP: 2001:db8::a1/---  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!
    		Network configuration UTMuser@firewall.name.fqdn Network
    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.
    It ist now possible that either

    • the leases are adapted and relocated in existing pools
      or
    • additional DHCP pools are created that contain static leases
      or
    • existing DHCP pools are extended so that they include static leases
    Warning at login

    In dieser Seite werden die Variablen für unterschiedliche Sprachen definiert.
    Diese Seite wird auf folgenden Seiten eingebunden









    {{var | Debug-Modus aktivieren--desc | Erst bei Aktivierung On werden Logmeldungen geschrieben | Log messages are only written when activated On | Dzienniki są zapisywane dopiero po aktywacji On }










    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.

    Setting up a DHCP relay for only one subnet of an interface
    1. If there are multiple subnets on an interface and a DHCP relay is to be created for only one of these subnets, this is only possible via VLANs.
    2. For this purpose, VLANs are created for the subnets of the interface. One with all subnets that should have a DHCP relay and one with the remaining subnets.
    3. Then, the corresponding VLAN can be selected as the client-side interface instead of the entire interface.
    Show example
    Hide example
    Klicken für dauerhafte Anzeige
    Let LAN2 be an interface with the following subnets
    • Subnet A with 192.168.1.0/24
    • Subnet B with 192.168.2.0/24
    • Subnet C with 192.168.3.0/24


    Now a DHCP relay is to be defined for subnets A and C, but not for B. For this purpose, a VLAN LAN2.1 is created, to which subnets A and C are assigned. A VLAN LAN2.2 is also created for B. So there are:

    • VLAN LAN2.1 with 192.168.1.0/24 and 192.168.3.0/24
    • VLAN LAN2.2 with 192.168.2.0/24

    With the DHCP relay, VLAN LAN2.1 is now selected as the client-side interface instead of LAN2
    Caption Value Description Network Configuration UTMuser@firewall.name.fqdn Network
    Network configuration DHCP relay overview
    activate Debug mode:
    notempty
    New as of v12.7.1
    		 Off

    DHCP Relay IPv4

    DHCP Relay IPv4
    DHCP server IP addresses:
    notempty
    updated
    Multiple entries possible
    		 »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.

    Overview of DHCP pools / leases

    notempty
    Path updated

    The Firewall Network topology menu provides an overview of assigned static leases and existing DHCP connections. Static leases can also be edited there directly.
    Further information can be found in the wiki article on network topology.


    Récupérée de "https://wiki.securepoint.de/index.php?title=UTM/NET/DHCP_Server-v6&oldid=116287"