Capsule install dhcp on eth1 interface

[fabriziolabanca]

Hello everyone.
In order to configure the DHCP service on the capsule (v.6.11) on eth1 interface, is it sufficient to run the classic command "--foreman-proxy-dhcp-interface eth1 etc. ..etc." or is it necessary to edit the file /etc/dhcp/dhcpd.conf and add eth1 and its subnet?
Eth1 must also be added on the web satellite as per the procedure redhat :

• In the Satellite web UI, navigate to Hosts > All hosts.
• Click Edit next to the host you want to edit.
• On the Interfaces tab, click Add Interface.
• Keep the Interface option selected in the Type list.
• Specify a MAC address. This setting is required.
• Specify the Device Identifier, for example eth0. The identifier is used to specify this physical interface when creating bonded interfaces, VLANs, and aliases.

thanks

[Travis · Accepted solution]

@fabriziolabanca -

I think you might be confusing some of the items in the lab with configuring Satellite or Capsule for being a PXE-Boot, DHCP provisioning system for hosts and hosts registering to Satellite for provisioning.

The satellite-installer command is capable of installing the packages and configuring either the built-in capsule on Satellite or the Satellite Capsule server with the provisioning services. This is done with the --foreman* options and is sufficient to install the packages and configure the services. There is no need to modifiy any files by hand to configure the DHCP or DNS services like you would if you were on a regular server.

The second task you mentioned with the Satellite WebUI is to provision/create a new host. The process you are describing is to create a new host record in Satellite for the provisioning to kickoff. You create the host with a name and parameters and give it the MAC address. When the host boots, it gets the DHCP address and it is authorized with Satellite and provisions based on the record you created.

[fabriziolabanca]

thank you for your reply;
I solved the problem: unfortunately I realised I had put in the wrong network address and now it worked.

Thanks again for your support

See you soon