Dynamic Host Configuration Protocol¶
Dynamic Host Configuration Protocol (DHCP) provides automatic addressing to clients.
TNSR can either allocate addresses to directly connected clients from a local DHCP daemon or it can act as a DHCP relay agent and forward address allocation requests to other DHCP servers.
DHCP Service Example¶
Configure the DHCP IPv4 Service from configuration mode (Configuration Mode). This example uses the interface and subnet from Example Configuration:
tnsr(config)# dhcp4 server
tnsr(config-kea-dhcp4)# description LAN DHCP Server
tnsr(config-kea-dhcp4)# interface listen GigabitEthernet0/14/2
tnsr(config-kea-dhcp4)# lease lfc-interval 3600
tnsr(config-kea-dhcp4)# option domain-name
tnsr(config-kea-dhcp4-opt)# data example.com
tnsr(config-kea-dhcp4-opt)# exit
tnsr(config-kea-dhcp4)# subnet 10.2.0.0/24
tnsr(config-kea-subnet4)# id 1
tnsr(config-kea-subnet4)# pool 10.2.0.128-10.2.0.191
tnsr(config-kea-subnet4-pool)# exit
tnsr(config-kea-subnet4)# interface GigabitEthernet0/14/2
tnsr(config-kea-subnet4)# option domain-name-servers
tnsr(config-kea-subnet4-opt)# data 8.8.8.8, 8.8.4.4
tnsr(config-kea-subnet4-opt)# exit
tnsr(config-kea-subnet4)# option routers
tnsr(config-kea-subnet4-opt)# data 10.2.0.1
tnsr(config-kea-subnet4-opt)# exit
tnsr(config-kea-subnet4)# exit
tnsr(config-kea-dhcp4)# exit
tnsr(config)# dhcp4 enable
tnsr(config)#
The above example configures example.com
as the domain name supplied to all
clients. For the specific subnet in the example, the TNSR IP address inside the
subnet is supplied by DHCP as the default gateway for clients, and DHCP will
instruct clients to use 8.8.8.8
and 8.8.4.4
for DNS servers.
Note
The subnet
definition requires an interface.