Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1iNFus-0004XT-KK for mharc-grub-devel@gnu.org; Wed, 23 Oct 2019 08:39:06 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36391) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iNFup-0004Tf-Eg for grub-devel@gnu.org; Wed, 23 Oct 2019 08:39:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iNFun-0007Fi-PG for grub-devel@gnu.org; Wed, 23 Oct 2019 08:39:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48888) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iNFun-0007EM-HP for grub-devel@gnu.org; Wed, 23 Oct 2019 08:39:01 -0400 Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2E5C685543 for ; Wed, 23 Oct 2019 12:39:00 +0000 (UTC) Received: by mail-wr1-f70.google.com with SMTP id 7so10942059wrl.2 for ; Wed, 23 Oct 2019 05:39:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XSpJ1uswi+ZyKoGTnWDdt3H5ZquR1TA1pVFLbRbrhac=; b=BqfRyn+TW1xo2EGR7ztYZXI2N9N6CMPbtDMptaQLoW+Ik9dxbhskqbYLEcn/O6Nb/T tL7mOloo5aDVh7B7TVcGMucXA3jlWZWZa7z9t51SGwErcX/Z6VBuv5/i2iyyGg3lUwEH 0PIIrPcWGDhinVRy4c+4nGpSxF/5cb41UADuBb/w6TKd3kefO9GI9VmTRasXoOtKlDNJ ANqRpRSY9Z+KL/WOEa7k0VQWFmuTty9scSo3eLQIM8dtXhprt8f9t979Yz/NzOVT56jp KvDEaxZxO8zTnb2Xdj6zZTSvVs+ZOYNjbn91xVEyuKcpgCBYU9KWlgf3GeazvLcCPDYj TYdQ== X-Gm-Message-State: APjAAAXtK5E/8FiVZ4mgVzVnIIzNOR7LQRGww7zrS+3KwoJFXis2co7+ 4EdI+75dbH1NDabijBv0SUevvIAYVs8qrLXvJuV1dJW/hnz0WRCHlQbcEl1yxKF8LBTq5hTaeJA Tf98K4PShfh0= X-Received: by 2002:a1c:96c9:: with SMTP id y192mr2239194wmd.8.1571834338868; Wed, 23 Oct 2019 05:38:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqz43sKhUNe6pAbK3oY2Mj33cLPxyR3hGcB0yEfNDJt9/I6PoMmw7QCiCPvK5938KIjU/ApruA== X-Received: by 2002:a1c:96c9:: with SMTP id y192mr2239161wmd.8.1571834338584; Wed, 23 Oct 2019 05:38:58 -0700 (PDT) Received: from [192.168.1.13] ([90.168.169.92]) by smtp.gmail.com with ESMTPSA id g5sm22309521wmg.12.2019.10.23.05.38.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Oct 2019 05:38:57 -0700 (PDT) Subject: Re: [PATCH v3 5/5] docs: Update info with grub.cfg netboot selection order To: Daniel Kiper Cc: grub-devel@gnu.org, Vladimir Serbinenko , Paulo Flabiano Smorigo , Robert Marshall References: <20191022084814.8071-1-javierm@redhat.com> <20191022084814.8071-6-javierm@redhat.com> <20191022142619.fssmpp6aczdik2hh@tomti.i.net-space.pl> From: Javier Martinez Canillas Message-ID: Date: Wed, 23 Oct 2019 14:38:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <20191022142619.fssmpp6aczdik2hh@tomti.i.net-space.pl> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Oct 2019 12:39:05 -0000 On 10/22/19 4:26 PM, Daniel Kiper wrote: > On Tue, Oct 22, 2019 at 10:48:14AM +0200, Javier Martinez Canillas wrote: >> From: Robert Marshall >> >> Add documentation to the grub info page that specifies the order >> netboot clients use to select a grub configuration file. >> >> Signed-off-by: Robert Marshall >> Signed-off-by: Javier Martinez Canillas > > Wow! We have a doc! Nice! > Yes, sorry for missing we had this and not including in the previous versions. [snip] >> + >> +@example >> +@group >> +@samp{(FWPATH)}/grub.cfg-@samp{(UUID OF NIC)} > > Hmmm... May each NIC have different UUID? I thought that UUID > is assigned to the machine not to the NIC. However, there is > a chance that I am missing something... > I think you are correct. The Client machine UUID option (97) isn't documented in RFC 2132, but in RFC 4578 and it just says the following about the UUID: 2.3. Client Machine Identifier Option Definition The format of the option is: Code Len Type Machine Identifier +----+-----+----+-----+ . . . +-----+ | 97 | n | t | | . . . | | +----+-----+----+-----+ . . . +-----+ Octet "t" describes the type of the machine identifier in the remaining octets in this option. 0 (zero) is the only value defined for this octet at the present time, and it describes the remaining octets as a 16-octet Globally Unique Identifier (GUID). Octet "n" is 17 for type 0. (One definition of GUID can be found in Appendix A of the EFI specification [4].) This option MUST be present in all DHCP and PXE packets sent by PXE- compliant clients and servers. Is the Client machine ID option (61) from RFC 2132 that says that a client ID MAY consistent of a hardware type and address. But it says that a hardware hardware type of 0 could also be used when the value field contains and ID that is not a hardware address. And that is up to the the vendors and system administrators to choose an ID that meets the requirement for uniqueness. In other words, it MUST be unique and MAY contain a hardware address but that may not necessarily be the case. I'm not the author of this patch but I guess that's the source of the confusion. I'll just change to mention that is the UUID of the machine and point to the RFC 4578. [snip] >> +@example >> +@group >> +@samp{(FWPATH)}/grub.cfg-7726a678-7fc0-4853-a4f6-c85ac36a120a >> +@samp{(FWPATH)}/grub.cfg-52-54-00-ec-33-81 >> +@samp{(FWPATH)}/grub.cfg-0A000082 >> +@samp{(FWPATH)}/grub.cfg-0A00008 >> +@samp{(FWPATH)}/grub.cfg-0A0000 >> +@samp{(FWPATH)}/grub.cfg-0A000 >> +@samp{(FWPATH)}/grub.cfg-0A00 >> +@samp{(FWPATH)}/grub.cfg-0A0 >> +@samp{(FWPATH)}/grub.cfg-0A >> +@samp{(FWPATH)}/grub.cfg-0 >> +@samp{(FWPATH)}/grub.cfg >> +@end group >> +@end example >> + > > Is it possible to assign both IPv6 and IPv4 addresses at once to the NIC? By looking at the networking code I believe that it's possible, although I have only tested this patch-set with IPv4. > What will happen if both are assigned? And first of all: does GRUB at The grub_net_search_config_file() function iterates over all the interfaces using the FOR_NET_NETWORK_LEVEL_INTERFACES() macro. So it will try to lookup a grub.cfg with the suffix for the IPv4 or IPv6 address depending on the order in which the interfaces were registered. > this point support IPv6? > My understanding is that GRUB does support IPv6. But for example DHCPv6 isn't supported. I've posted the patches we have to add DHCPv6 to bootp and efinet. > Daniel > Best regards, -- Javier Martinez Canillas Software Engineer - Desktop Hardware Enablement Red Hat