I spotted that OVMF completely ignores the configured IPv4 static IP settings, for PXE and HTTP boot, and just uses DHCP anyway. (Confirmed on various versions from edk2-stable201905 to current master.)
When looking at the user-readable paths for PXE and HTTP boot options, it seems likely that this is indeed the intended behaviour: PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0) PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri() Furthermore, PXE 2.1 spec (e.g. §2.2.1) gives no indication PXE boot is supposed to work with static IP, and while it is less clear it seems somewhat similar for HTTP boot in UEFI specification (e.g. v2.10 §24.7.4). Hence to my questions, if anyone has time to answer: 1. Is it correct that the static IP settings available in OVMF are intended to be ignored for PXE and HTTP boot? 2. Is there any (documented?) way to set a static IP for PXE or HTTP boot? (With HTTP boot, in particular, we can already set the boot URI in the path, so if we could set the IPv4 addr/mask/gateway/dns then we could boot without DHCP.) 3. If it's not too general to ask, what types of application are the IP settings intended for, if not PXE/HTTP boot? Just other IP-based applications, in general, I guess? Thanks in advance for any help! -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#120891): https://edk2.groups.io/g/devel/message/120891 Mute This Topic: https://groups.io/mt/110033368/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
