3 ms·
TFTP is crazy slow, even with RFC 7740 (buffering), but the payloads are usually small so few people care. Thankfully modern BIOSes tend to implement HTTP boot
by pzmarzly 11mo ago
TFTP is crazy slow, even with RFC 7740 (buffering), but the payloads are usually small so few people care.
Thankfully modern BIOSes tend to implement HTTP boot option, where you can point to any HTTP or HTTPS URL (as long as the URL ends with ".efi", which is a pretty dumb limitation if you ask me).
- pjc50 11mo agoThey let you boot off HTTPS? That explains why corp IT pushed out a Dell BIOS vulnerability update today relating to OpenSSL in my BIOS.
- kotaKat 11mo agoYup! You can point your BIOS at a .efi and it’ll Just Boot It. We’ve even got Wi-Fi support in some of these as well for a full wireless deploy… https://www.dell.com/support/manuals/en-us/bios-connect/https_ug/introduction-to-https-boot?guid=guid-dbc85161-a46f-4c9f-97bd-2134b37c0dce&lang=en-us https://www.dell.com/support/manuals/en-us/bios-connect/http...
- legooolas 11mo agoYou can also do things like boot with PXE (Legacy or UEFI PXE boot) to get a small image like iPXE, and then have iPXE do the http boot part. This means that you have an extra shim but you can pull larger images than TFTP is any good for. TFTP is also UDP and I don't think it is pipelined, so it's all req->ack->req->ack, so any additional latency hits it hard too.