DHCP Server

Description

This module installs and configures the DHCP server deamon

Release notes

Show release notes
Version 2.4.3 - General deployment
  • Bugfix: Removed error message when installing the module when not activated (M10835)
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.4.2 - Early deployment
  • Bugfix: Default values could be incorrect when upgrading from a previous version and new options are available. (M10261)
  • Improvement: When installing the module unconfigured, the install failure message is now more explicit (M9975)
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.4.1 - Early deployment
  • Bugfix: DHCP configuration was not generated on the standby SOPs after an apply-change
  • Bugfix: DHCP server was started on standby clone after the reinstallation of the module
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.4.0 - Early deployment
  • Feature: Allow to ignore config without writing the network definition in the configuration file (M8150)
  • Feature: Correctly generating error files for the DHCP configuration probe (M8495)
  • Bugfix: Configuration was not correctly generated when putting phone in different VLAN than SOPs with other default gateway (M8410)
  • Improvement: Reduce module installation time on high latency networks (M8766)
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.3.1 - General deployment
  • Bugfix: DHCP server process was started on a standby SOP after an Apply Changes (M8066)
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.3.0 - General deployment
  • Feature: Support DHCP options for LG-Ericsson IP phones (M7602)
  • Feature: Dynamic configuration of DHCP through resources (M7507)
  • Feature: Configurable domain name (M6937)
  • Improvement: Allow the same syntax for extended subnets as in the default subnet parameters
  • Bugfix: DHCP options for SNOM phones were incorrect (M5629)
  • Dependency:
    • Database Schema module >= 1.27.0
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)
    • SOP Base module >= 1.4.2

Version 2.2.0 - General deployment
  • Feature: Allow HTTP/HTTPS provisoning for Polycom phones (M6262)
  • Bugfix: Packages were not cached between SOP reboots (M7066)
  • Dependency:
    • SOP Base module >= 1.4.2
    • Polycom Phone support module version 4.5.0 or higher (Optional: only for HTTP(S) provisioning)

Version 2.1.5 - General deployment
  • Bugfix: Vlan creation doesn't work if there is only 1 vlan configured (M6232)
  • Dependency:
    • SOP Base module >= 1.4.2
    • SMP >= 4.9.0

Version 2.1.4 - Deprecated
  • Feature: Allows to define more than 15 subnets (M0005739)
  • Feature: Allows to deactivate the dhcp server (M0)
  • Deprecated: Config with only 1 subnet does not work (M00006232)
  • Dependency:
    • SOP Base module >= 1.4.2

Version 2.1.3 - General deployment
  • Bugfix: DHCP option for Snom phones was not correct (M5629)
  • Dependency:
    • SOP Base module >= 1.4.2

Version 2.1.2 - General deployment
  • Bugfix: Fixed error showed in debug log at first install of the module (M0005216)
  • Bugfix: Install all the dependencies with dhcp-server package (M0004982)
  • Bugfix: Install all the dependencies with dhcp-server package (M0005269)
  • Dependency:
    • SOP Base module >= 1.4.2

Version 2.1.1 - General deployment
  • Feature: Added support for cisco phones (M0004870)

Version 2.1.0 - General deployment
  • Feature: Added support for Baseline 2.0 (M0003103)

Version 2.0.2 - General deployment
  • Bug fix: install process blocks on dpkg interactive question

Version 2.0.1 - Deprecated
  • Bug fix: Removing old configuration files (M0003073)
  • Deprecated: Install process blocked which causes eternal install modules

Version 2.0.0 - Deprecated
  • Feature: Potential update impact level 3 DONE: in the event this update contains a bug, it might have critical impact. ERROR! Given the complexity of the update, it is advised to contact ESCAUX support before applying this update. Support for offering netmask and gateway different from netmask and gateway of the sop. (M2034)
  • Deprecated: Install process blocked which causes eternal install modules

Version 1.5.0 - General deployment
  • Feature: Support for offering netmask and gateway different from netmask and gateway of the sop. (M2034)

Version 1.4.0 - General deployment
  • Potential update impact level 2 DONE: in the event this update contains a bug, it might have critical impact. Respect dependencies and retest your most important callflows and applicative integrations.
  • DHCP options for Polycom phone support
  • DHCP options for Mitel phone support
  • Validation of DNS server input
  • Changed search domain to 'escaux.local'

Version 1.3.0 - General deployment

Version 1.2.0 - General deployment
  • Improvement: Better default configuration

Version 1.1.0 - General deployment
  • Feature: Initial version

Module configuration interface

create_resource_form: .:/usr/share/escaux/glue/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib/

Range first IP
Range last IP
TFTP server
Default lease time (seconds)
Maximum lease time (seconds)
Netmask to offer
Default gateway to offer
Subnet 1
Subnet 2
Subnet 3
Subnet 4
Subnet 5
Subnet 6
Subnet 7
Subnet 8
Subnet 9
Subnet 10
Subnet 11
Subnet 12
Subnet 13
Subnet 14
Subnet 15
Extended subnets
deactivate DHCP server
Protocol to use for provisionong Polycom phones
Domain name

Module configuration parameters

Numbered subnets

  • Range first IP: First IP address of the range (pool) of IPs that we want to assign to DHCP clients.
  • Range last IP: Last IP address of the range (pool) of IPs that we want to assign to DHCP clients.
  • TFTP server: Leave this field empty to use the SOP's TFTP server.
  • Default lease time (seconds): Leave this field empty to keep the standard 6 hour default lease time.
  • Maximum lease time (seconds): Leave this field empty to keep the standard 12 hour maximum lease time.

New in 2.x. DHCPD v3 in order to support DHCP relay agent. This enables a SOP to provide dynamic addresses to different VLANs.

  • Subnet X: Describe a subnet and its DHCP parameters on the format of key-value pairs separated by semi-columns:
    • range: Range IP address that we want to assign to DHCP clients
    • subnet: Subnet of the network interface or the DHCP relay agent
    • netmask: Netmask of the network interface or the DHCP relay agent
    • tftp-server: The tftp server IP to indicate in the DHCP options
    • routers: The default router to be offered to the DHCP client
    • subnet-mask: The netmask to be offered to the DHCP client
    • default-lease: The default-lease time of the offered IP address
    • max-lease: The maximum lease time of the offered IP address

Example: 
Subnet 1: subnet=172.18.64.0;netmask=255.255.255.0;range=172.18.64.100 172.18.64.200;routers=172.18.64.1;subnet-mask=255.255.255.0;tftp-server=172.18.64.10;default-lease=21600;max-lease=43200

Extended subnets

If you need more than 15 subnets, you have to use the extended subnets field. The options (range, subnet, ...) are the same as for numbered subnets but the syntax is different. Each subnet is written on a line and parameters are separated by ';'.

The order of the parameters matters and every parameter must be defined.

  • Subnet X: Describe a subnet and its DHCP parameters
    • range: Range IP address that we want to assign to DHCP clients
    • subnet: Subnet of the network interface or the DHCP relay agent
    • netmask: Netmask of the network interface or the DHCP relay agent
    • tftp-server: The tftp server IP to indicate in the DHCP options
    • routers: The default router to be offered to the DHCP client
    • subnet-mask: The netmask to be offered to the DHCP client
    • default-lease: The default-lease time of the offered IP address
    • max-lease: The maximum lease time of the offered IP address

Domain name: you can configure the DHCP parameter "option domain-name" here. This parameter will be applied to all subnets defined in the module. The default value is "escaux.local".

ALERT!Starting with version 2.3.0 of the module you can also use the same syntax as for normal subnets in the extended subnets parameter.

Before 2.3.0

Example : 
192.168.1.1 192.168.1.254;192.168.1.0;255.255.255.0;10.0.1.1;10.0.1.254;255.255.255.0;64800;125600
192.168.2.1 192.168.2.254;192.168.2.0;255.255.255.0;10.0.1.1;10.0.1.254;255.255.255.0;64800;125600
In this case you have 2 subnets 192.168.1.0 and 192.168.2.0.

After 2.3.0

Example: 
subnet=172.18.64.0;netmask=255.255.255.0;range=172.18.64.100 172.18.64.200;routers=172.18.64.1;subnet-mask=255.255.255.0;tftp-server=172.18.64.10;default-lease=21600;max-lease=43200
subnet=172.18.68.0;netmask=255.255.255.0;range=172.18.68.100 172.18.68.200;routers=172.18.68.1;subnet-mask=255.255.255.0;tftp-server=172.18.68.10;default-lease=21600;max-lease=43200

Provisioning for Polycom Phones

  • Protocol to use for provisioning Polycom phones: you can chose which protocol to use for provisioning Polycom phones. This parameter must be coherent with the parameter set in the Polycom Phone Support module. See Secure Telephony Administrator Guide for the extra steps needed.

Post-install actions

In case this module is installed on a Baseline 1 High Availability SOP that is currently in standby mode, you need to use the shell plugin to deactivate the processes. This is available in the High Availability module version > 2.6.0.

Shell plugin

This module installs a shell plugin.

dhcpserver.PNG

It adds the menu DHCP server into the Subsystems main menu. You can find in this menu :
  • An option to start the DHCP server
  • An option to stop the DHCP server
  • An option to show the DHCP server leases.

Activate/Deactivate

To activate the DHCP server, simply install the module with the setting 'deactivate DHCP server' to 'no'.

There is currently no way to remove the module but you can disable it by setting 'deactivate DHCP server' to 'yes'.

Make DHCP server listen on a specific interface

By default, if the ip address of the SOP isn't in one of the defined subnets, the DHCP server won't listen incoming packet on its interface.

In order to run a DHCP server with DHCP relay without impacting the local subnet where the DHCP is, you can define a numbered subnet with no range. It will make the DHCP server listen on its interface but it won't respond to request coming from the subnet which has an empty definition.

To define a subnet with an empty body you need to define the 'subnet' and the 'netmask' attributes and nothing else.

Example : 
subnet=172.18.64.0;netmask=255.255.255.0

Copyright © Escaux SA