Assignment 1: DHCP service

DHCP server

Install and configure the DHCP service on server-01. This allows us to keep the network configuration parameters of every client host on only one host; the DHCP server

1. Installation: (1)

   • isc-dhcp-server

2. Configuration: After that, configure it:

   • Configure your DHCP service as authoritative for your subnet.

   • Define for your DHCP service only one network (subnet) which can serve network configurations to clients belonging to the network 10.128.0.0. Main parameters:

     • Default lease time: 120

     • Máximum lease time: 600

     • Gateway IP: 10.128.0.1

     • Network mask IP: 255.255.255.0

     • Broadcast IP : 10.128.0.255

     • Domain name: localdomain

     • DNS server IPs: 169.254.169.254 (2), 10.128.0.11

     • NTP server: time.google.com (3)

     • Dynamic IP range: from 10.128.0.180 to 10.128.0.200 (both included)

   • And now, for each client of our subnet, add its DHCP configuration to the file /etc/dhcp/dhcpd.conf (according to their @ 'mac') to assign network configuration in a statical way.

     • frontend.localdomain: 10.128.0.100

3. Post-installation:

   • Service will be started for IPv4 operation only, and ens4 network interface.

     • Make sure that GCP environment (firewall) allows DHCP traffic on network 10.128.0.0.

More details in reference [1]

DHCP Client

Check that the frontend links correctly with the DHCP server on server-01:

1. Use the dhclient command from frontend to renew its network setting through (fixing) the DHCP server to server-01. Monitor this process through system log files on server-01 (tail) or using it in a debugging mode.

   • Has the IP been renewed? Why? ... Try to monitor the DHCP proccess (dialog) using log files and verbose mode.

2. Use again the dhclient command from frontend to renew network setting without specific server:

   • What happen now?

   • What the IP of DHCP server that attend to the frontend?

More details in references [7][8]

(1) Use the official debian software repositories.

(2) We will use the metadata server of Google (GCP).

(3) Temporally.