> _______________________________________________ > > It is included in Arachne. Let me quote. > > First from wattcp\src\readme.2nd: > > "The bootp code now supports dhcp." > ----------------------------------------------- > > First BOOTP doesn't support DHCP; DHCP supports BOOTP ... protocol says > it has to be backwards compatible with BOOTP. The change(s) made must > have been to bring BOOTP up to last standards before everything switched > to DHCP. Independent programs report that BOOTP was being used [not > DHCP]. You are right, DHCP is a superset of BOOTP, but the quote is also correct as it refers to the "bootp code". When I wrote that note, I specifically meant that I added the ability to negotiate parameters from a DHCP server using modifications to the existing BOOTP code in WATTCP. The BOOTP code in WATTCP 9911A now adds the "DHCP DISCOVER" vendor option. If there's a DHCP server out there, it will respond and WATTCP will go through the DHCP handshake. If there's a BOOTP server out there configured for the requestors MAC address, I make the assumtion that it will ignore the DHCP option and respond anyway with a standard BOOTP reply thus causing WATTCP to behave like it always has.
