can you elaborate more? how would we find the specific host entry based on a range?

In the case of just one interface, you have to know the mac address, dhcp or not, to identify the good host at foreman level (when templating kickstart).

If you have 2 interfaces, only one of them is generally used for installation, not both. For the other one, there is fewer chances to have a second DHCP setup that will attribute IP/netmask/gw in this LAN.

In that case, the 2nd mac address is useless as it is not important during the installation process. therefore for templating the kickstart the netmask parameter of this second interface is usefull.

If we extend the perimeter to 'n' interfaces, only one will be used for installations (but not necessary the first one). The others can be :
- statically configured : in this case the netmask parameter is crucial. Other information such as gateway/specific routes can be customised by the user with parameters, I dont think a specific code should include these.
- configured by DHCP out of scope of foreman
- configured by DHCP with the current smart proxy of the host (how to find next available IP in this case?)
- configured by DHCP with another smart proxy because of network isolation, blablabla (how to find next available IP in this case?)

I'd like to concentrate this feature on the 2nd nic statically configured as it is my current issue.

If you have multiple IPs on a single NIC, the mac address doesn't add anything either.