On 2010/3/17 下午 06:56, Michael Brown wrote: > On Wednesday 17 Mar 2010 09:20:32 Steven Shiau wrote: >> The problem is, the MAC addresses might change. For example, if you are >> testing some new machines, especially in the massive deployment, batch >> to batch, you won't like the idea to input the MAC addresses in the >> dhcpd config file. >> >> My question is, why gPXE differs in the DHCP Client ID? Why it's not the >> same with etherboot or PXE? > > gPXE passes the link-layer address in the DHCP client identifier (as per RFC > 2132 section 9.14). > > This is a legacy of Infiniband support; it used to be the case that the client > identifier was the only way to identify an IPoIB DHCP request, since the 20- > byte IPoIB MAC address is too long for the 16-byte chaddr field (see RFC > 4390). > However, gPXE now fills the chaddr field with the 8-byte Infiniband GUID, so > this > problem no longer exists. > > gPXE continues to set the DHCP client identifier for backwards compatibility. Any option I can turn it off? Make it like what PXE or Etherboot does? Thanks.
Steven. > > Michael -- Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
