How To Configure DHCP Server

From Userful Support
Jump to: navigation, search


Copyright © 2019 Userful Corporation. All rights reserved.
(Updated 2018.01.30)


To return to the main documentation page, Click Here.


Introduction

The Userful Control Center allows systems that have two network adapters to create a stripped down subnet intended to isolate traffic from the corporate intranet. In certain cases doing this improves the overall stability of the network as TCP/IP traffic going to the zero clients will not compete for bandwidth with regular internet / intranet traffic.


Please Note that the newly created subnet is a heavily stripped down subnet, meant only for zero client devices. No DNS or gateway is provided and is necessary. Network traffic in that subnet should not cross to the other adapter and vice versa.

Steps to configure DHCP server

Configuring DHCP Server


  • Open Control Center and navigate to Settings > Network Settings tab and click the "Edit" button next to the network interface intended to be used for the subnet.


  • Select the "Manual Network Config" option and configure the static address of the network card to the desired address. When created, the DHCP server will use the values entered to create the DHCP scope. For more details, refer to DHCP Server Details section.


  • Click the “Enable a DHCP Server on this network interface” checkbox to turn it on.


  • Click Save to complete the process


DHCP Server Details

When the DHCP server is created, the static address assigned to the network adapter is declared as reserved and the server consumes the whole subnet excluding the one reserved.

For example: if the network interface is configured for 192.168.10.10 / 255.255.255.0, then the DHCP server will be configured to serve 192.168.10.1 to 192.168.10.254 on the 255.255.255.0 subnet with 192.168.10.10 reserved for the network adapter that the static address is configured on (therefore no IP conflicts occur).

To ensure that the packets are routed correctly, it is strongly recommended that the configured DHCP be given a unique subnet that does not overlap the intranet that the other network card is connected to. For example, if the other network card is on a 192.168.1.x / 255.255.255.0 subnet, then the isolated NIC could be assigned 192.168.2.1 / 255.255.255.0 with the 192.168.2.x subnet being used for the isolated network.


Related Links