Network Client Management
Network Client Management covers DHCP and centralized authentication clients: PAM, LDAP, and SSSD. The exam checks whether you can configure a client to obtain addressing and authenticate against a directory without breaking local logins.
Core rules
dhcpd.confusessubnet,range,option routers,option domain-name-servers,default-lease-time, andmax-lease-time. Fixed addresses use ahoststanza withhardware ethernetandfixed-address.dhcpd -ttests syntax; leases are indhcpd.leases.- PAM stacks in
/etc/pam.d/are read top-down. Module types areauth,account,password, andsession; controls includerequired,requisite,sufficient, andoptional.pam_unixhandles local files;pam_ldaporpam_sssadds directory auth. - LDAP client config uses
URI,BASE, and TLS settings in/etc/ldap/ldap.conf(or/etc/openldap/ldap.conf). SSSD uses/etc/sssd/sssd.confwithid_provider,auth_provider, andldap_uri; startsssdand test withgetent passwd user. - Keep a local fallback: a broken LDAP/SSSD stack can lock out SSH if PAM has no
sufficient pam_unixpath.
Worked example
Reserve 192.0.2.50 for a printer with MAC 00:11:22:33:44:55 in a 192.0.2.0/24 scope. Add host printer { hardware ethernet 00:11:22:33:44:55; fixed-address 192.0.2.50; } inside the subnet, ensure the dynamic range excludes .50, run dhcpd -t, reload. Reasoning: the server matches the MAC before offering a dynamic lease; an address inside the pool can cause conflicts unless excluded.
Traps
Missing semicolons in dhcpd.conf; forgetting authoritative on the only DHCP server; PAM module order that lets requisite deny before a later sufficient; LDAP TLS certificates not trusted; and SSSD not enabled/started, so getent never sees directory users.