public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Mike Beaton via groups.io" <mjsbeaton=gmail.com@groups.io>
To: devel@edk2.groups.io
Subject: [edk2-devel] Static IP for PXE/HTTP boot
Date: Tue, 10 Dec 2024 21:28:28 +0000	[thread overview]
Message-ID: <CAHzAAWR_8BnWFmHmn3v0X5u+KGtV1YE8zbbt0fGA6aAQN5tBtA@mail.gmail.com> (raw)

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/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



                 reply	other threads:[~2024-12-10 21:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHzAAWR_8BnWFmHmn3v0X5u+KGtV1YE8zbbt0fGA6aAQN5tBtA@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox