From: "Cohen, Eugene" <eugene@hp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Wu, Jiaxin" <jiaxin.wu@intel.com>
Subject: DHCP Automatic Configure at Driver Connect
Date: Wed, 10 Aug 2016 18:17:12 +0000 [thread overview]
Message-ID: <AT5PR84MB02917CE953A461F419CC0A2EB41D0@AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM> (raw)
With this commit:
Revision: 1f6729ffe98095107ce82e67a4a0209674601a90
Author: jiaxinwu <jiaxin.wu@intel.com>
Date: 7/7/2015 2:19:55 AM
Message:
MdeModulePkg: Update Ip4Dxe driver to support Ip4Config2 protocol,
a new behavior seemed to come in to the network stack that was not present before: It appears now that as soon as the DHCP Service Binding protocol is installed the DHCP process will be initiated (see Ip4Config2OnDhcp4SbInstalled). This differs from past behavior where DHCP would only occur if a driver or application specifically did Configure() on the network interface.
For some systems this is problematic because they need to defer DHCP until it is certain that the network interface will be used for something.
Can you provide the reason for this change? Can we have a policy (PCD) to disable this mode of operation?
Thanks,
Eugene
next reply other threads:[~2016-08-10 18:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 18:17 Cohen, Eugene [this message]
2016-08-11 1:50 ` DHCP Automatic Configure at Driver Connect Wu, Jiaxin
2016-08-11 3:03 ` Ye, Ting
2016-08-11 5:59 ` Wu, Jiaxin
2016-08-11 14:22 ` Cohen, Eugene
2016-08-11 15:20 ` Samer El Haj Mahmoud
2016-08-12 1:31 ` Wu, Jiaxin
2016-08-12 12:31 ` Cohen, Eugene
2016-08-13 2:37 ` Wu, Jiaxin
2016-08-15 14:40 ` Cohen, Eugene
2016-08-16 3:05 ` Wu, Jiaxin
2016-08-16 19:41 ` Cohen, Eugene
2016-08-17 5:50 ` Wu, Jiaxin
2016-08-17 12:17 ` Cohen, Eugene
2016-08-18 2:48 ` Wu, Jiaxin
2016-08-18 3:10 ` Ye, Ting
2016-08-18 14:30 ` Cohen, Eugene
2016-08-16 1:14 ` Ye, Ting
2016-08-16 19:19 ` Cohen, Eugene
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=AT5PR84MB02917CE953A461F419CC0A2EB41D0@AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.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