From: Mark Rutland <mark.rutland@arm.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: "Rivard, Matthew T" <matthew.t.rivard@intel.com>
Subject: Re: [PATCH][WiP] native DHCPv4 support in net_bootp
Date: Thu, 21 Jan 2016 18:37:37 +0000 [thread overview]
Message-ID: <20160121183737.GI2581@leverpostej> (raw)
In-Reply-To: <569BB641.4040609@gmail.com>
Hi,
Thank you for putting this together!
On Sun, Jan 17, 2016 at 06:41:53PM +0300, Andrei Borzenkov wrote:
> 14.10.2015 23:09, Andrei Borzenkov пишет:
> > 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.
> >
>
> This patch adds support for native DHCPv4 and removes requirement for
> BOOTP compatibility support in DHCP server.
>
> This is work in progress, but this works for me in test environment.
I haven't delved into the code, but FWIW, this also works for me in my
BOOTP-free work environment on an AArch64 host:
grub> insmod efinet
grub> net_ls_cards
efinet1 00:00:1a:1b:9d:9a
efinet0 00:00:1a:1b:9d:99
grub> net_bootp efinet0
grub> insmod tftp
grub> set net_default_server=10.1.205.151
grub> linux (tftp)/Image
grub> boot
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 4.4.0-rc3+ (mark@leverpostej) (gcc version 5.1.1 20150608 (Linaro GCC 5.1-2015.08) ) #63 SMP PREEMPT Mon Jan 18 10:20:30 GMT 2016
....
I have not tested BOOTP as I do not have a BOOTP server to hand.
I'd like to be able to net-boot a number of development machines that I am in
charge of. However, as I'm not in charge of the network I cannot use PXE, and
our DHCP servers do not implement BOOTP.
Having DHCP support would be incredibly useful for being able to net-boot
boards in a standard manner while not having full control over the network.
> Patch changes net_bootp to implement full DHCP transaction. it still
> /should/ work with BOOTP pure server (untested, I do not have one). It
> also re-implements option processing to support overloaded fields and
> consolidates it in one place.
>
> What is currently not implemented
>
> - per interface, per transaction stage retransmit timer. Will be done.
>
> - DHCP server selection. We take first DHCPOFFER or BOOTPREPLY. No plans
> to implement.
>
> - DHCP option concatenation (RFC3396). I do not expect to hit it in real
> life; could be implemented relatively easy if needed.
>
> - client identifier (RFC6842). I do not expect to hit it in real life;
> could be added easily if needed.
The above sounds fine for my purposes.
Thanks,
Mark.
next prev parent reply other threads:[~2016-01-21 18:45 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
2016-01-17 15:41 ` [PATCH][WiP] native DHCPv4 support in net_bootp Andrei Borzenkov
2016-01-21 18:37 ` Mark Rutland [this message]
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=20160121183737.GI2581@leverpostej \
--to=mark.rutland@arm.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.