Next: Top Menu Up: DHCP Previous: DHCP Contents
This menu permits the definition of subnets to be served and the parameters of the network configurations to attribute to the workstations. (Figure 7.43)
At the top menu you have links to Insert new subnets, configure Redundancy parameters and define the General Options. You also have a list of the inserted subnets. Each IP is a link that displays the configuration options in each one (Figure 7.44).
Insert
The Insert links allows you to introduce subnet parameters, which shall be attributed to the clients:
DHCP Type: Select if your DHCP server is Local or Remote.
Local: By default, IPBRICK's DHCP server is set to local, if you wish to centralize a database of available IP addresses and networks for various servers it is advised to configure the Master server as Local DHCP and its Slave(s) as Remote.
Remote: At the Slave server you will have to delete the local DHCP settings and insert a remote DHCP server that will fetch its network settings from the local DHCP server, avoiding thus the arduous task of configuring independently a new network.
Remote new form options will appear, where you will have to insert the Network address, the address of your network and the Master Server that hosts the Local DHCP server.
Network Address: It allows you to indicate the address of the network and the respective mask;
Dynamic addresses range: Which range of addresses is reserved to attribute the clients;
Clients mask: Mask of the network to attribute the clients;
Broadcast address: Address of broadcast to attribute the clients;
Default lease time: Default lease time during which the address can be lent;
Max lease time: Max lease time of an IP address for the machines. This value surpassed, the IP address is renewed;
Default Gateway: Address of the gateway which will serve as the default route (by default 192.168.69.199);
DNS Servers: List (one per line) of the DNS servers to be used by the clients (by default ipbrick.domain.com);
WINS servers: List (one per line) of the WINS servers to be used by the clients (by default ipbrick.domain.com);
TFTP server: Define the TFTP server to be used by DHCP clients. Can be used for example for IP phones auto provisioning;
Image Server: This server hosts the image replication service for Linux user stations. This way every machine can be updated without the need for individual and manual OS updates.
Boot File: The boot file enables the user machine to restart via the image server. It is the individual boot file in every Linux machine, including data such as its MAC address. Each machine is thus identified by the image server, which in turn will proceed with the appropriate updating procedure. By default, the Linux boot file is: pxelinux.0
DNS domain: Name of the domain indicated to the clients (by default domain.com).
Redundancy
It is possible for an IP network to configure two DHCP servers, one as main (primary) server and the other as secondary. Normally, only the primary server answers the requests, while the secondary one synchronizes its DB with the primary, if the primary fails the secondary shall assume its service. Communication between the servers is made from the network ports which may be customized. One of the ports shall be attending the connections from the secondary server and the other one shall be attending the connections from the main server. (Figure 7.46)