+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: Configuring iPXE to DHCP probe a specific interface (/showthread.php?tid=11123)
Configuring iPXE to DHCP probe a specific interface - louied - 2018-04-04 20:47
Hello all, I have a machine with two external 10G NICs and an internal interface. I will only be booting iPXE from one of the 10G NICs so I was wondering if there was some way to possibly have iPXE only probe and send DHCP requests from that one specific interface rather than it cycle through all three each time.
RE: Configuring iPXE to DHCP probe a specific interface - NiKiZe - 2018-04-04 20:53
If it is always that same nic, and iPXE is booted from some local device, then you could have an embeded script that loops over the interfaces and checks the mac before booting that device.
However if you chainload iPXE over the network in the first place, then try snponly.efi (assuming efi here) - that should make it only have that same nic, not multiple ones.
To give more proper examples, could you give us more information about what platform you are booting (pcbios/efi), what nics it is, how iPXE is booted, and which build target of iPXE you are using.
RE: Configuring iPXE to DHCP probe a specific interface - louied - 2018-04-05 01:17
(2018-04-04 20:53)NiKiZe Wrote: If it is always that same nic, and iPXE is booted from some local device, then you could have an embeded script that loops over the interfaces and checks the mac before booting that device.
However if you chainload iPXE over the network in the first place, then try snponly.efi (assuming efi here) - that should make it only have that same nic, not multiple ones.
To give more proper examples, could you give us more information about what platform you are booting (pcbios/efi), what nics it is, how iPXE is booted, and which build target of iPXE you are using.
Ah I see, yeah iPXE is being chainloaded over the network and it is a UEFI environment. I just tried using snponly.efi and it seems to have done the trick. Thank you!