From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.24; helo=mga09.intel.com; envelope-from=siyuan.fu@intel.com; receiver=edk2-devel@lists.01.org Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 411872095E519 for ; Mon, 25 Sep 2017 00:55:19 -0700 (PDT) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Sep 2017 00:58:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,435,1500966000"; d="scan'208,217";a="903528737" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by FMSMGA003.fm.intel.com with ESMTP; 25 Sep 2017 00:58:29 -0700 Received: from fmsmsx158.amr.corp.intel.com (10.18.116.75) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 25 Sep 2017 00:58:29 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx158.amr.corp.intel.com (10.18.116.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 25 Sep 2017 00:58:29 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.152]) with mapi id 14.03.0319.002; Mon, 25 Sep 2017 15:58:27 +0800 From: "Fu, Siyuan" To: Karunakar P , "'edk2-devel@lists.01.org'" CC: "Wu, Jiaxin" , "Ye, Ting" Thread-Topic: Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring DHCP server as per RFC3021 Thread-Index: AdM1yawo0+R1yhiITlaLRJLRbEJqXQACDGqwAACA0JA= Date: Mon, 25 Sep 2017 07:58:26 +0000 Message-ID: References: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring DHCP server as per RFC3021 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2017 07:55:20 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Karunakar May I know that whether you have a real requirement that must use the point= -2-point link in your environment, or you just found this problem in your t= est? BestRegards Fu Siyuan From: Fu, Siyuan Sent: Monday, September 25, 2017 3:50 PM To: Karunakar P ; 'edk2-devel@lists.01.org' Cc: Wu, Jiaxin ; Ye, Ting Subject: RE: Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring= DHCP server as per RFC3021 Hi, Karunakar You are correct that EDK2 doesn't support rfc3201. The most obvious problem that come to my mind is the NetIp4IsUnicast() func= tion in NetLib, which has the assumption that the host address part should = not be all zero or all one (or to say, -1 in the rfc3201). I think that's w= hy the PXE failed, but Cent OS could use IP address from the same DHCP serv= er. This is just an example, there may be some other places in edk2 network sta= ck which have the same assumption, I'm not sure about this. Anyway, we neve= r considered the point-2-point link in edk2. BestRegards Fu Siyuan From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Monday, September 25, 2017 3:02 PM To: 'edk2-devel@lists.01.org' > Cc: Wu, Jiaxin >; Fu, Siyua= n >; Ye, Ting > Subject: Re: Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring= DHCP server as per RFC3021 Hello All, It is known that current EDKII doesn't support RFC3021, We could see the fo= llowing behavior which is PXE boot fails whereas Cent OS can get IP address= from the same BIOS. [Configuration Used] DHCP server setting under Ubuntu: 1. /etc/dhcp/dhcpd.conf # RFC3021-Using 31-bit perfixes on IPv4 Point-to-Point Links subnet 192.168.1.0 netmask 255.255.255.254 { range 192.168.1.1 192.168.1.1; next-server 192.168.1.0; filename "EFI/BOOT/BOOTAA64.EFI"; option subnet-mask 255.255.255.254; option routers 192.168.1.0; } 2. /etc/network/interfaces auto eth0 iface eth0 inet static address 192.168.1.0 netmask 255.255.255.254 network 192.168.1.0 If the DHCP server and network interface are set up above configuration. Be= low are my test results and questions 1. CentOS 7.3 (pre-installed) was able to retrieve IP through DHCP wh= en they connect HDD to the SUT where PXE is failing. 2. Could you please suggest what could be the reason behind this? Thanks, karunakar