From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=203.199.198.232; helo=imsva.in.megatrends.com; envelope-from=karunakarp@amiindia.co.in; receiver=edk2-devel@lists.01.org Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 C871C21E43B43 for ; Mon, 25 Sep 2017 01:51:20 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E090082047; Mon, 25 Sep 2017 14:27:13 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BFD5D82046; Mon, 25 Sep 2017 14:27:13 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Mon, 25 Sep 2017 14:27:13 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Mon, 25 Sep 2017 14:24:28 +0530 From: Karunakar P To: "'Fu, Siyuan'" , "'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: AQHTNdQYEwAPyyWDikKXk6PJMke3l6LFSg+A Date: Mon, 25 Sep 2017 08:54:27 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.128] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23350.005 X-TM-AS-Result: No--16.318-5.0-31-10 X-imss-scan-details: No--16.318-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23350.005 X-TMASE-Result: 10--16.317900-10.000000 X-TMASE-MatchedRID: oCj5caaCQyk6yy6RAAEPc+YAh37ZsBDC1kqyrcMalqU5bxeAKHFV2Hcj c/4RjcGN87b8c06nz5VuIha8OLwqaEwPFQLh4g6A2OSj4qJA9QYTiAXE61uSubV5fSMRD1zqHAf +6Nm9yXObw95fe9m+IPXGsMQPBBPT9pSZB+rA6ONVTfJWlqPdDOU28KlVaRfjZJY6r7aDSHbMJo 0JaBiNPN0mpA1Khc2MWX6smM8uy4EgKhvx00H1wRcqpH7D1rtQSpaOqiMX04D/AS4zo8w8NUzcW R/oWb15DyWMzCss/oBfk7lCgHOgtVwbcxoyLgaZfKmN9+B2Aw8h/JA0dHadpnQ8D+SLaQjsHEkR fST+Ts4uI29Z9XjQN+eJm6LClLmHwisXXd5ilGuKC6Im4I1RF/hs+N+bSEhB4pinC0b7AdXwWEa NOnlY9/L8w9/9GZdKhW2BDI+9Fsw0nIDKoCZxv3uTVkeYosXtuacNrbMY+LS17wx8kgvnlE8ROU aX64h0kIR5jQkue1Tl22c7vF4Nm32wZ99SrtsMy7TSWcbz49YxmlBLt0TR1oJy/meScoY1hQH+Y spUfFp2+AZuxakJy1x59CtgmyHsWcbhowRxPdMvj6wHfIGxyS2VljVYB9GNVNFVtrDWmzo4BNeS qPakobtWFqyDCQRSFABeLgZr0ZEfE8yM4pjsD/7E6GNqs6ceAaUQk5EZOUlFGCd0S0NCskz583g pOSaqVTSO83ojknnXLLDhY+DnEqKwtmd3+k0ZxYVzI3UCCaY= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-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 08:51:21 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Fu Siyuan, Thanks for your conformation. We would like to use /31s to save IPv4 addresses. When it's a point-to-point link (server to router), the extra network addre= ss and broadcast address is wasted. RFC 3021 solves the problem by using a broadcast address of 255.255.255.255= on such subnets. We have a requirement to support this, do you have any plan to support RFC3= 021 ? Given the requirement time consuming how hard to implement this ? Thanks, karunakar From: Fu, Siyuan [mailto:siyuan.fu@intel.com] Sent: Monday, September 25, 2017 1:28 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 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 w= hen they connect HDD to the SUT where PXE is failing. 2. Could you please suggest what could be the reason behind this? Thanks, karunakar