From Fedora Project Wiki

Revision as of 16:25, 17 August 2023 by Sumantrom (talk | contribs) (Created page with "{{QA/Test_Case |description=This test case ensures that the `dhcp-client` package is working as expected. It verifies that a client machine can request, receive, and use an IP address from a DHCP server. |setup= # Install the version of Fedora that is to be tested on a bare metal or virtual system. # Install the `dhcp-client` package using the command: `sudo dnf install dhcp-client`. |actions= # Connect the client machine to a network with a functioning DHCP server. # Op...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

This test case ensures that the dhcp-client package is working as expected. It verifies that a client machine can request, receive, and use an IP address from a DHCP server.

Setup

  1. Install the version of Fedora that is to be tested on a bare metal or virtual system.
  2. Install the dhcp-client package using the command: sudo dnf install dhcp-client.

How to test

  1. Connect the client machine to a network with a functioning DHCP server.
  2. Open a terminal window.
  3. Run the command sudo dhclient <network-interface> to request a DHCP lease, where <network-interface> is your network interface name (e.g., eth0, ens33).
  4. Run the command ip a or ifconfig to verify that the client machine has received an IP address from the DHCP server.

Expected Results

  1. The dhclient command completes without error.
  2. The client machine successfully receives an IP address from the DHCP server.
  3. The client machine can communicate with other machines on the network using the assigned IP address.
  4. The DHCP lease information is correctly stored (usually in /var/lib/dhclient or similar directory).

Optional

  1. Test the DHCP lease renewal process by observing the client machine over an extended period and ensuring it maintains network connectivity.
  2. Test the behavior when the DHCP server is unreachable or not responding to requests.
  3. Test the behavior with different DHCP server configurations (e.g., static leases, different subnets).