public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Fu, Siyuan" <siyuan.fu@intel.com>
To: Karunakar P <karunakarp@amiindia.co.in>,
	"'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Cc: "Wu, Jiaxin" <jiaxin.wu@intel.com>, "Ye, Ting" <ting.ye@intel.com>
Subject: Re: Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring DHCP server as per RFC3021
Date: Mon, 25 Sep 2017 07:50:30 +0000	[thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B3C0277@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <A885E3F3F1F22B44AF7CC779C062228EE068831A@VENUS1.in.megatrends.com>

Hi, Karunakar

You are correct that EDK2 doesn't support rfc3201.

The most obvious problem that come to my mind is the NetIp4IsUnicast() function 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 why the PXE failed, but Cent OS could use IP address from the same DHCP server.

This is just an example, there may be some other places in edk2 network stack which have the same assumption, I'm not sure about this. Anyway, we never 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' <edk2-devel@lists.01.org>
Cc: Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>; Ye, Ting <ting.ye@intel.com>
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 following 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. Below are my test results and questions


1.      CentOS  7.3 (pre-installed) was able to retrieve IP through DHCP when they connect HDD to the SUT where PXE is failing.

2.      Could you please suggest what could be the reason behind this?


Thanks,
karunakar


  parent reply	other threads:[~2017-09-25  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  7:02 Linux CentOS 7.3 can get DHCP IPv4 IP address with configuring DHCP server as per RFC3021 Karunakar P
2017-09-25  7:18 ` Ye, Ting
2017-09-25  7:50 ` Fu, Siyuan [this message]
2017-09-25  7:58 ` Fu, Siyuan
2017-09-25  8:54   ` Karunakar P
2017-09-27  8:15     ` Fu, Siyuan
2017-09-27  9:36       ` Karunakar P
2017-10-16  7:12         ` Karunakar P

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-list 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=B1FF2E9001CE9041BD10B825821D5BC58B3C0277@SHSMSX103.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox