GNU GRUB - Bugs: bug #65250, GRUB unable to PXE boot
You are not allowed to post comments on this tracker with your current authentication level.
bug #65250: GRUB unable to PXE boot
Submitter: | Qiumiao Zhang <century6> | ||
Submitted: | Sun 04 Feb 2024 07:01:23 AM UTC | ||
Category: | Network | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | century6 |
Open/Closed: | Open | Release: | Git master |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-02a9.
Corresponding source code
Versions affected: 2.04, 2.06
Reproduced on: UEFI PXE with DHCPv6 Relay Agent
Tested on: QEMU virtual machine (x86_64) with Linux
A DHCPv6 relay agent, which may reside on the client's link, is used to relay messages between the client and the server. It allows a DHCPv6 client to send a message to a DHCPv6 server that is not connected to the same link.
In the PXE scenario, if the client and server are not connected to the same link, grub2 needs to configure the default gateway after requesting an IP address from the server through a DHCPv6 relay agent, otherwise grub2 does not know which network interface to use to send tftp requests.
I think grub2 needs to send an ICMPv6 (type 133) Router Solicitation (RS) message to inquire about the local IPv6-capable router on the network. In response to the RS, the router immediately sends an ICMPv6 (type 134) Routing Advertisement (RA) message, then grub2 can configure the default gateway through the RA message. And perhaps this process should be done in the function of grub_efi_net_config_real(). Is this feasible?