From: Santhapur Naveen <naveens@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Madhan B. Santharam" <madhans@ami.com>,
Sivaraman Nainar <sivaramann@amiindia.co.in>
Subject: Classless IP support for IPv4 PXE boot
Date: Wed, 17 Aug 2016 11:41:08 +0000 [thread overview]
Message-ID: <625A2455CC232F40B0F38F05ACED6D976C4DA5CE@VENUS1.in.megatrends.com> (raw)
Hello,
We happened to observe that the IPv4 PXE boot was happening successfully for both classless and classful IPs until the EDKII revision 21542. It has been found that there are some changes made in the revision 21543 and the IPv4 PXE boot is failing for classless IP addresses. The failure scenario was debugged and is explained here. Let's assume the subnet range is 192.168.1.0/16. The DHCP server tries to allot an IP (let's say 192.168.1.0) but based on the first byte of the IP address to be assigned, the function NetGetIpClass() returns the IP class as Class-C and its respective subnet mask as 255.255.255.0 that should be for a classful IP address whereas 255.255.0.0 is the actual subnet in this scenario. The changes present in function Dhcp4InstanceConfigUdpIo() seems to be responsible for the failure.
May we know the reason behind the changes present in the Dhcp4Impl.c of the revision 21543? Is there any plan to bring the classless IP support in NetworkPkg?
Thanks,
Naveen
next reply other threads:[~2016-08-17 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 11:41 Santhapur Naveen [this message]
2016-08-18 2:48 ` Classless IP support for IPv4 PXE boot Fu, Siyuan
2016-08-18 2:53 ` Ye, Ting
2016-08-18 3:15 ` Santhapur Naveen
2016-08-18 3:20 ` Fu, Siyuan
2016-08-18 3:27 ` Wu, Jiaxin
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=625A2455CC232F40B0F38F05ACED6D976C4DA5CE@VENUS1.in.megatrends.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