Hi Michael, Sorry I missed your previous email. First, I don't use OVMF platform, though I think the PXE and HTTP should be able to co-work together. It means that the PXE boot option and HTTP boot option are both available in the boot manager of BDS. I might not fully understand your usage, though. Second, the UEFI spec defines EFI_IP4_CONFIG2_PROTOCOL for user to configure and retrieve DNS server addresses. You could use GetData with data type "Ip4Config2DataTypeDnsServer" to retrieve the info. Also, you can use EFI_DNS4/6_PROTOCOL to translate the host name to IP address directly. In the case you don't know the DNS server address, just configure the DnsServerList to NULL when configuring the DNS protocol instance; the protocol will try to retrieve the DNS server address from DHCP server.
Thanks, Ye Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Michael Chang Sent: Friday, May 20, 2016 12:57 PM To: edk2-devel@lists.01.org Subject: Re: [edk2] UEFI HTTP Boot Device Path and DNS Gently ping .. Could anyone help to provide insights for this? In short the URI is absoultely legit to have host name in it but current device path couldn't provide any dns server to help in resolving it. How to deal with this problem ? Thanks, Michael On Tue, Apr 19, 2016 at 06:18:35PM +0800, Michael Chang wrote: > Background (And also Question): > The PXE Base Code Protocol is no longer produced if selecting to boot > from UEFI HTTP device from boot menu. Does anyone here know why or is > it's just a problem of my environment (I'm using OVMF from openSUSE) ? > > That made the work to support it in grub2 more complicated than it > should be, becuase it has to extract DHCP information from dhcp > packets cached in EFI_PXE_BASE_CODE_MODE structure to setup it's own > network interface. That's how it works before for TFTP, and at that > time booted TFTP device path seems to provide meaningless values. > > Question: > Now that we have to get it work by taking another approach to obtain > the DHCP information from the booted (HTTP) URI device path if the PXE > BC protocol cannot be located. But then we also bumped into another > issue that DNS infomation is missing from within the device path nodes > like > (MAC(..)/IPv4(...)/URI(..)) so that server name in URI cannot work but > can only use IP address (v4 or v6). Is this a spec issue or intended > to leave behind DNS info ? > > Could anyone please help to provide more insights ? > > Thanks. :) > Michael > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
