We're using Kea and iPXE to do cross-site provisioning so I'm not sure what's not working for you. One thing I did run into early in testing was having to use the kpxe shim (I think that's the suffix, it's one of the binary variants generated by the makefile and not the default one) because the DHCP request packet from iPXE and preseed were subtly different enough that Kea would create two leases ... but once we got that, it's been solid to the tune of several hundred devices ... I can share parts of my config if you're interested; I did end up using a beta version in our application because it had additional option parsing logic operators, but those have been merged into the released version in the meantime. cheers,Klaus
Sent from my tri-corder On Thu, Jan 5, 2017 at 9:19 AM -0800, "Ledochowski, Roy" <[email protected]> wrote: HI all- I am looking into replacing ISC DHCPd with Kea in our dev lab. One of the primary requirements is iPXE chainloading - in other words, the PXE ROM on the NIC must be able to download and execute iPXE over the network. >From packet dumps, it appears that Kea is using the unicast MAC address in the >destination in DHCP offers. This works for the NIC's PXE ROM, and loads iPXE >but iPXE rejects the offers because it expects the broadcast MAC address. As >a result iPXE never gets an IP address and fails to execute. I've setup a simple test environment in VMware Workstation 12.5: | ---------------- | | Kea 1.1 VM | ens37 | CentOS 7 |----------------------| Test VM | ---------------- | | ens33 | | outside The interface configuration is "interfaces-config": { "interfaces": [ "ens37" ] } I have the packet captures if anyone is interested. Any help is much appreciated and thanks ahead of time, roy _______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
