It turns out that it gets the TFTP server ip from the next-server option of the DHCP. Maybe, this should be emphasized in the wiki.
2010/6/5 Ozan Yerli <[email protected]>: > Thanks for the nice explanation. > > I have another question. In the wiki page: > http://etherboot.org/wiki/winpe it says in order to load the files > from the TFTP server add the following option to the DHCP server: > filename "\\Boot\\pxeboot.n12"; > > But this does not contain any server ip. How will the gPXE know the > address of the TFTP server? Do I also need to add another command to > give the TFTP server? > > > 2010/6/5 Miller, Shao <[email protected]>: >> Good day again Ozan, >> >> The point is that your SAN should have its MBR zeroed out. keep-san >> will tell gPXE "try to SAN-boot, but if that fails, leave the SAN >> connected and leave the SAN params in memory, for a later OS to find, if >> needed." >> >> The zeroed MBR will return you to gPXE, from which you then chain the >> Windows NBP. >> >> Windows' iSCSI support will find the SAN params in memory and attach the >> SAN. >> >> - Shao Miller >> > _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
