From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by ml01.01.org (Postfix) with ESMTP id F35D01A1DED for ; Wed, 10 Aug 2016 18:50:14 -0700 (PDT) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP; 10 Aug 2016 18:50:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,502,1464678000"; d="scan'208";a="153965271" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga004.fm.intel.com with ESMTP; 10 Aug 2016 18:50:06 -0700 Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 10 Aug 2016 18:50:06 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX112.amr.corp.intel.com (10.18.116.6) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 10 Aug 2016 18:50:06 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.181]) by shsmsx102.ccr.corp.intel.com ([169.254.2.147]) with mapi id 14.03.0248.002; Thu, 11 Aug 2016 09:50:04 +0800 From: "Wu, Jiaxin" To: "Cohen, Eugene" , "edk2-devel@lists.01.org" , "Ye, Ting" Thread-Topic: DHCP Automatic Configure at Driver Connect Thread-Index: AdHzMrTK7bp7ndKxTJOq/Qc4XXghzQAOAqZg Date: Thu, 11 Aug 2016 01:50:03 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B7274137C5D67@SHSMSX103.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTdhZGEzN2YtYzA1NS00ZWZhLTg1OWEtMzBhYTg1MzM1MWJmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS45LjYuNiIsIlRydXN0ZWRMYWJlbEhhc2giOiI2dzBicDVHYmhoRDRNQk5xTnl2VkVwXC9wTUVCNDhDazNvWEhpR0JtYkM0OD0ifQ== x-ctpclassification: CTP_PUBLIC x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: DHCP Automatic Configure at Driver Connect X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2016 01:50:15 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Eugene, The default policy is static, DHCPSB will not be installed automatically. = Currently, there are only two cases that DHCP process will be triggered. On= e is Ip4Config2 policy change to DHCP, and another one is any IP4 configure= instance set UseDefaultAddress to TRUE, detailed see Ip4StartAutoConfig().= So, I don't quite understand your question about the differs behavior com= pared to before. I think the current behavior of Ip4Config2 DHCP also need = the third specifically configuration. Thanks, Jiaxin > -----Original Message----- > From: Cohen, Eugene [mailto:eugene@hp.com] > Sent: Thursday, August 11, 2016 2:17 AM > To: edk2-devel@lists.01.org; Wu, Jiaxin > Subject: DHCP Automatic Configure at Driver Connect >=20 > With this commit: >=20 > Revision: 1f6729ffe98095107ce82e67a4a0209674601a90 > Author: jiaxinwu > Date: 7/7/2015 2:19:55 AM > Message: > MdeModulePkg: Update Ip4Dxe driver to support Ip4Config2 protocol, >=20 > 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 DHC= P > would only occur if a driver or application specifically did Configure() = on the > network interface. >=20 > For some systems this is problematic because they need to defer DHCP unti= l > it is certain that the network interface will be used for something. >=20 > Can you provide the reason for this change? Can we have a policy (PCD) t= o > disable this mode of operation? >=20 > Thanks, >=20 > Eugene >=20