Xinetd and TFTP1972. Then, the administrator creates a class called PXE, which, if a system that is configured to havePXE first in its boot priority, identifies itself as PXEClient.3. Then DHCP server then directs the system to the Cobbler server at 192.168.2.1.4. Finally, the DHCP server refers to the boot image file (in this case, at /var/lib/tftpboot/pxelinux.0.11.1.4. Xinetd and TFTPXinetd is a daemon that manages a suite of services, including TFTP, the FTP server used fortransferring the boot image to a PXE client.To configure TFTP, you must first enable the service via Xinetd. To do this, edit the /etc/xinetd.d/tftp as root and change the disable = yes line to disable = no.Before TFTP can start serving the pxelinux.0 boot image, you must start the Xinetd service.chkconfig --level 345 xinetd on/sbin/service xinetd startThe chkconfig command turns on the xinetd service for all user runlevels, while the /sbin/service command turns on xinetd immediately.11.1.5. Configuring SELinux and IPTables for Cobbler SupportRed Hat Enterprise Linux is installed with SELinux support in addition to secure firewall enabledby default. To properly configure a Red Hat Enterprise Linux server to use Cobbler, you must firstconfigure these system and network safeguards to allow connections to and from the Cobbler Server.11.1.5.1. SELinux ConfigurationTo enable SELinux for Cobbler support, you must set the SELinux boolean to allow HTTPD webservice components. Run the following command as root on the Cobbler server:setsebool -P httpd_can_network_connect trueThe -P switch is essential, as it enables HTTPD connection persistently across all system reboots.You must also set SELinux file context rules to ensure Cobbler properly functions in an SELinuxsystem.Run the following as root on the Cobbler server:semanage fcontext -a -t public_content_t "var/lib/tftpboot/.*"The command sets file context for TFTP to serve the boot image file.
