[ipxe-devel] Windows having problems parsing iBFT from recent iPXE versions?

[Floris Bos]

On 10/29/2014 11:44 AM, Floris Bos wrote:
> Both have nameserver filled in.
> One difference does seem to be that the new iPXE sets the origin to 3 
> (IpPrefixOriginDhcp) while the older one sets it to 0 
> (IpPrefixOriginOther)
>
> Not sure if Windows acts differently on that.

Did some more testing, and the origin does not not seem the problem.
Reversed the patch that changed that, and it didn't fix the problem.


Another strange thing I did notice is that Windows after boot does send 
out DHCP requests, but never accepts the lease offered:

==
Oct 29 12:29:49 minx local7.info dhcpd: DHCPOFFER on 192.168.178.4 to 
08:00:27:23:27:ac via eth0
Oct 29 12:29:53 minx local7.info dhcpd: DHCPDISCOVER from 
08:00:27:23:27:ac via eth0
Oct 29 12:29:53 minx local7.info dhcpd: DHCPOFFER on 192.168.178.4 to 
08:00:27:23:27:ac via eth0
Oct 29 12:30:01 minx local7.info dhcpd: DHCPDISCOVER from 
08:00:27:23:27:ac via eth0
Oct 29 12:30:01 minx local7.info dhcpd: DHCPOFFER on 192.168.178.4 to 
08:00:27:23:27:ac via eth0
==

It also makes ARP requests for the IP of the iSCSI SAN:

==
13:39:59.666349 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:39:59.666366 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:39:59.666534 ARP, Reply 192.168.178.99 is-at 00:11:32:26:ac:0e (oui 
Unknown), length 46
13:40:00.384921 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:40:00.384936 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:40:00.385064 ARP, Reply 192.168.178.99 is-at 00:11:32:26:ac:0e (oui 
Unknown), length 46
13:40:01.385017 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:40:01.385035 ARP, Request who-has 192.168.178.99 tell 192.168.178.4, 
length 28
13:40:01.385202 ARP, Reply 192.168.178.99 is-at 00:11:32:26:ac:0e (oui 
Unknown), length 46
==

But doesn't seem to receive the reply, as it is asking again.
Like Windows can send out packets, but does not receive them.

This only happens when performing an iSCSI boot through the new iPXE 
version.
If I perform a Windows network installation through the new iPXE 
version, but without iSCSI, networking does work fine.

-- 
Yours sincerely,

Floris Bos