From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Rivard, Matthew T" <matthew.t.rivard@intel.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: iPXE efi chainloading grub2 pxe efi file
Date: Wed, 14 Oct 2015 23:09:58 +0300 [thread overview]
Message-ID: <561EB696.5070909@gmail.com> (raw)
In-Reply-To: <EEEB59C9688B214382E250B0063276B96EF03B@ORSMSX102.amr.corp.intel.com>
14.10.2015 21:09, Rivard, Matthew T пишет:
> Just going by these definitions of bootp and dhcp here:
> https://technet.microsoft.com/en-us/library/cc781243%28v=ws.10%29.aspx
>
> The net_bootp only works with a bootp enabled scope on the dhcp server after chaining from iPXE to grub2. Without a "bootp" scope setup on the dhcp, calling net_bootp on the adapter fails to get an IP address.
>
> So, I guess I could more clearly word that the bootp protocol works when calling net_bootp, but standard dhcp isn't.
>
Hmm ... you are right; we are actually doing BOOTP here, not DHCP.
next prev parent reply other threads:[~2015-10-14 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EEEB59C9688B214382E250B0063276B96CEE43@ORSMSX102.amr.corp.intel.com>
[not found] ` <55FB8A5F.6040404@gmail.com>
[not found] ` <EEEB59C9688B214382E250B0063276B96CF050@ORSMSX102.amr.corp.intel.com>
2015-10-14 6:13 ` iPXE efi chainloading grub2 pxe efi file Andrei Borzenkov
2015-10-14 16:56 ` Rivard, Matthew T
2015-10-14 18:03 ` Andrei Borzenkov
2015-10-14 18:09 ` Rivard, Matthew T
2015-10-14 18:23 ` Andrei Borzenkov
2015-10-14 21:12 ` Rivard, Matthew T
2015-10-14 20:09 ` Andrei Borzenkov [this message]
2016-01-17 15:41 ` [PATCH][WiP] native DHCPv4 support in net_bootp Andrei Borzenkov
2016-01-21 18:37 ` Mark Rutland
2016-03-19 1:03 ` Rivard, Matthew T
2016-03-19 4:51 ` Andrei Borzenkov
2015-10-15 17:46 ` [ipxe-devel] iPXE efi chainloading grub2 pxe efi file Michael Brown
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-all 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=561EB696.5070909@gmail.com \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=matthew.t.rivard@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.