Bug #12892
closed
``HTTPClient`` option not sent when using UEFI HTTP Boot
Added by Ben Breard almost 3 years ago.
Updated over 1 year ago.
Plus Target Version:
22.05
Description
Hey thanks for adding support HTTP Boot from issue 11659. I couldn't make it work w/ my systems and notice from a packet capture that HTTPClient isn't being sent as option 60 (vendor-class-identifier). If I manually add that as an additional option (additional option -> 60 -> text -> HTTPClient), everything works as it should. I believe this option should be automatically added when a user adds an NBP to enable HTTP Boot. Otherwise it's not intuitive why systems won't boot from the network.
Cheers
- Target version set to 2.7.0
- Plus Target Version set to 22.05
- Related to Feature #11659: Support for UEFI HTTP Boot option in DHCPv4 Server added
- Assignee set to Viktor Gurov
- Status changed from New to Pull Request Review
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
Tested against:
2.7.0-DEVELOPMENT (amd64)
built on Sat Mar 05 06:18:38 UTC 2022
FreeBSD 12.3-STABLE
After enablig Network Boot, the option 60 type text is automatically added into /var/dhcpd/etc/dhcpd.conf file.
option custom-lan-0 code 60 = text;
I am marking this ticket resolved.
- Status changed from Resolved to New
- Status changed from New to Pull Request Review
- Status changed from Pull Request Review to Feedback
- Subject changed from HTTPClient not sent when UEFI HTTP Boot to ``HTTPClient`` option not sent when using UEFI HTTP Boot
Updating subject for release notes.
- Status changed from Feedback to Resolved
Tested on the:
2.7.0-DEVELOPMENT (amd64)
built on Fri Apr 08 06:16:19 UTC 2022
FreeBSD 12.3-STABLE
Looks good! Ticket resolved.
- Subject changed from ``HTTPClient`` option not sent when using UEFI HTTP Boot to ``HTTPClient`` option not sent when using UEFI HTTP Boot
Also available in: Atom
PDF
Updated by 
Updated by Viktor Gurov 
Updated by