Date: Tue, 2 May 2017 00:58:56 +0000 From: rgrimes <phabric-noreply@FreeBSD.org> To: freebsd-net@freebsd.org Subject: [Differential] D10485: Replace dhcp option 150 by 66 Message-ID: <7ab6e55a9d2090a6a81311f7f0a37f6d@localhost.localdomain> In-Reply-To: <differential-rev-PHID-DREV-rdfe23ryefhflnjblbcr-req@FreeBSD.org> References: <differential-rev-PHID-DREV-rdfe23ryefhflnjblbcr-req@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
rgrimes added a comment. The more I look at PXE and DHCP the sicker I get. Your right, a client well not normally request option 150, for that matter I am not sure it well request 66 either, though I suspect many do, and probably many of them also wrongly interpret that as a dotted quad when it is actually a host name. I have had to fuss with dhcp servers and pxe clients for days if not weeks to get some operating systems booting over the network. Right now I can boot almost any FreeBSD >9 version as long as I am not an a UEFI platform, so our code is not that broken, I do have to use loader code from -head on the older releases, so things have improved. My use case is rather narrow I suppose in that I always chain load to iPXE to use its advanced features vs what most cards have in there bios. I am getting freebsd's pxeboot via tftp, then use that to get the kernel via nfs. Again, can we get input from Bapt who did the addition of opt 150 and how it worked? REVISION DETAIL https://reviews.freebsd.org/D10485 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: kczekirda, bapt, oshogbo, tsoome, sbruno, #network, freebsd-net-list, imp, jhb Cc: rgrimes, garga, ler, asomershelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7ab6e55a9d2090a6a81311f7f0a37f6d>