[ipxe-devel] iPXE doesn't load when using ISC Kea 1.1

Ledochowski, Roy roy.ledochowski at hpe.com
Thu Jan 12 00:07:23 GMT 2017


HI Geert-

Somehow this ended up in my junkmail.  I don't quite understand your reply " Easy said advice:
  Leave the partly broken path,
  focus on the partly working path."  Can you give more details please?


-----Original Message-----
From: ipxe-devel-bounces at lists.ipxe.org [mailto:ipxe-devel-bounces at lists.ipxe.org] On Behalf Of Geert Stappers
Sent: Thursday, January 05, 2017 1:29 PM
To: ipxe-devel at lists.ipxe.org
Subject: Re: [ipxe-devel] iPXE doesn't load when using ISC Kea 1.1

On Thu, Jan 05, 2017 at 09:09:10PM +0000, Ledochowski, Roy wrote:
> From: Geert Stappers, Sent: Thursday, January 05, 2017 12:32 PM
> > On Thu, Jan 05, 2017 at 05:08:37PM +0000, Ledochowski, Roy wrote:
> > > 
> > > I sent the two captures to you directly.
> > > 
> > 
> > Yes, got them.
> > 
> > Where I missed in the original posting in the DHCP offer a value for 
> > parameter 67, bootfilename, is that value missing both in the 
> > working and _non_ working dhcp server.
> > 
> > Other observations:
> > 
> > * iPXE is being loaded as undionly.kpxe for the "original bootROM"
> > * the "original bootROM" is happy with both unicast and broadcast 
> > DHCP offers
> > * in the working configuration there is twice "DHCP Discover plus DHCP Offer",
> >   the "original bootROM" does only once "DHCP Discover plus DHCP offer"
> > * iPXE does four "DHCP Discovers". Packets 111, 113,117 and 119
> > * Kea does four "DHCP Offers". Packets 112, 114, 118 and 120
> > 
> > 
> > And the most interresting observation is packet 116 in the Kea.pcap, 
> > which is a reply on packet 115 in capture file.
> > 
> > 115: DHCP server doing an ARP request for the iPXE client
> > 116: the iPXE client ARP replying "I have that IPv4 address"
> > 
> > $ /usr/sbin/tcpdump -nr kea.pcap arp | $( some_filtering )
> > 01:02:27.978877 ARP, Request who-has 10.1.1.124 tell 10.1.1.20, 
> > length 28
> > 01:02:27.979055 ARP, Reply 10.1.1.124 is-at 00:0c:29:73:f2:92, 
> > length 46
> > 
> > So some part of the the DHCP offer from kea is processed correctly.
> > 
> 
> Hi again
> 
> I've tested it with sending the 'file' option alone and with 'file'
> and option 67.  Kea fails both tests in the same manner.  DHCPd 
> succeeds with only the 'file' option as expected.
> 

Easy said advice:
  Leave the partly broken path,
  focus on the partly working path.

The ARP packets, in the original post as
 16:15:37.410799 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.1.1.124 tell ickyhut, length 28
 16:15:37.410919 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.1.1.124 is-at 00:0c:29:73:f2:92 (oui Unknown), length 46 proof that iPXE understands something from Kea.


Cheers
Geert Stappers
--
Leven en laten leven
_______________________________________________
ipxe-devel mailing list
ipxe-devel at lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel


More information about the ipxe-devel mailing list