From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0730.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe46::730]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 040AA1A1DF5 for ; Thu, 11 Aug 2016 07:31:04 -0700 (PDT) Received: from AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.25) by AT5PR84MB0289.NAMPRD84.PROD.OUTLOOK.COM (10.162.138.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Thu, 11 Aug 2016 14:31:00 +0000 Received: from AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.25]) by AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM ([10.162.138.25]) with mapi id 15.01.0549.025; Thu, 11 Aug 2016 14:31:00 +0000 From: "Cohen, Eugene" To: "Wu, Jiaxin" , "edk2-devel@lists.01.org" Thread-Topic: IP4 Config Troubles with DHCP Thread-Index: AdHzLtnEw2gfDCBbQ1OtxXknLLKMhQAabX6gABD3ncA= Date: Thu, 11 Aug 2016 14:31:00 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B7274137C5EF1@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274137C5EF1@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=eugene@hp.com; x-originating-ip: [15.65.254.4] x-ms-office365-filtering-correlation-id: fbf1d5ba-9918-4459-87b3-08d3c1f41dff x-microsoft-exchange-diagnostics: 1; AT5PR84MB0289; 6:cwEyDYQEb+iUrVGLQdlOGPmTR7ZKndk/5xtJcg0AiETsAcpigeZ9MeW05CXyQydm/Y4Oo3N0Evd+pYM4LdCiW/S7dpNHGHukaEbfv2Uuduso+7wp43JTxqLGeZkTWpHmMRr6gNuYIemR96rds3U4rqDpFkF32q3l+g94+5H/It8gE9jr6dA76nHKroouFMQRtxU/oS3IMOdH77f35rdxt8JGKK0rVpJSWq3CDdTFX+tmHjBSPk8SgCd+POuIeooqU8D2Zt9N5RITP38EIrAzLx71W+WDlWk+7fNwV+fVez4=; 5:gZIcAoon6fMgbbv+/scfR40M9AhS49UQmdpXrSd1GqlUO5qXGHm3CJh6ghL40LCo99lP0vdMawpzIYP407OfNIWf8IfcrcvlACCimbDpBJUXdjIwZWmVmFoyD+YWC9iXvrehInKDV31rX365iD2EeQ==; 24:PPPaPJ2c0yCuFswHdYklyosv4xzJ+B5IjyGczNvr9pAn3cj6Nm9eAljDjE0VH6/bVYKF7NglW2SdqZKQRmjvI2pT9zVLK7C4I4A5tDAau4w=; 7:d3TG5ADVAt1CIm+XvvL5kaJ9GnFbTldX/vzwqnnaIFtadKHwEkGqAmqe4L063UCM7RacHLU4Wx08Cvsv/QHr6hhM2NsXoyDrJR2tJaMBWruSRlgHF/kKx35kqOpFnP3eSNW84RbxN9E4g3s1KQAJp81Lu7G++0YoWmDjvkPxVtzvCYjash05xeLuHOAcncoQVmYj3GrARHJKkYUbdMUONzO62ojTlzJVdu6/+SrHW45KyML0jfxe0C5nunnYclV4 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AT5PR84MB0289; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:AT5PR84MB0289; BCL:0; PCL:0; RULEID:; SRVR:AT5PR84MB0289; x-forefront-prvs: 0031A0FFAF x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(6602003)(76176999)(102836003)(11100500001)(5002640100001)(101416001)(50986999)(6116002)(54356999)(3846002)(99286002)(3280700002)(105586002)(97736004)(3660700001)(2906002)(92566002)(66066001)(2950100001)(106356001)(107886002)(87936001)(2900100001)(7736002)(77096005)(9686002)(33656002)(68736007)(8936002)(189998001)(86362001)(81156014)(81166006)(7846002)(7696003)(305945005)(122556002)(74316002)(8676002)(5001770100001)(10400500002)(2501003)(586003)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:AT5PR84MB0289; H:AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: hp.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hp.com X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Aug 2016 14:31:00.7317 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ca7981a2-785a-463d-b82a-3db87dfc3ce6 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AT5PR84MB0289 Subject: Re: IP4 Config Troubles with DHCP 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 14:31:04 -0000 Content-Language: en-US Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Jianxin, > I want to confirm with you the steps to reproduce the issue: >=20 > 1. Set policy to DHCP. > 2. If DHCP process is not complete yet, then run one App to invoke the > UDP4 Configure with "UseDefaultAddress =3D TRUE" (loop to keep calling > Udp4->Configure until Ip4Mode.IsConfigured changes to TRUE) > 3. Even DHCP succeed but Ip4Mode.IsConfigured flag never set to > TRUE ---- failure here!!! >=20 > Above steps right? Yes, that summarizes it well. > Actually, you don't need to retry the UDP configuration loop according > the Ip4Mode.IsConfigured flag. You are only recommended to set a > timer to check the mapping status after the configuration: This is exactly what we used to do. Recently it stopped working which is w= hy we now have to re-do service binding creation and configuration. > If DHCP process succeed, Ip4Mode.IsConfigured should be updated. If > not, any bug may be existed. >>From the traces I've looked at I can clearly see that the DHCP process as f= inished (lease acquired) and that Ip4Mode.IsConfigured is still FALSE. I'l= l send you a detailed trace of this separately. So yes, I think there is a bug that crept in. Eugene