From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.115; helo=mga14.intel.com; envelope-from=jiaxin.wu@intel.com; receiver=edk2-devel@lists.01.org Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 06EC320945C00 for ; Mon, 9 Oct 2017 19:33:15 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2017 19:36:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,502,1500966000"; d="scan'208,217";a="1204073217" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga001.fm.intel.com with ESMTP; 09 Oct 2017 19:36:43 -0700 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 9 Oct 2017 19:36:43 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 9 Oct 2017 19:36:42 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.93]) with mapi id 14.03.0319.002; Tue, 10 Oct 2017 10:36:41 +0800 From: "Wu, Jiaxin" To: Karunakar P , "'edk2-devel@lists.01.org'" CC: "Fu, Siyuan" , "Ye, Ting" Thread-Topic: Request to display Initiator IP in ISCSI Attempt Page Thread-Index: AdM+g2+O9RDq7g5lRPGdGn5u7GUKPgC6t+Bg Date: Tue, 10 Oct 2017 02:36:40 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B72741633C764@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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMWY3MTdhN2QtOTliZS00ZjI2LTgzODMtYjUwNTY5MjJiMzkzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Ik9RSGpMT3B2YU50aUNNejVtb0J6V0NZS1hiQmZ0a2JNa29HNlQ2NDlHdzg9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: Request to display Initiator IP in ISCSI Attempt Page X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2017 02:33:16 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Karunakar, We agree to add this feature for the Initiator info of IPv4 when DHCP enabl= ed. Can you report it on Bugzilla first? To achieve that, we can grayout the Initiator IP/Subnet/Gateway if Initiat= or DHCP enabled to indicate it's un-configurable. For IPv6, since iSCSI onl= y request the target info from DHCP server, so, it's unnecessary to display= the info as IPv4. Thanks, Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Friday, October 6, 2017 5:28 PM To: 'edk2-devel@lists.01.org' Cc: Fu, Siyuan ; Wu, Jiaxin ; Ye,= Ting Subject: RE: Request to display Initiator IP in ISCSI Attempt Page Hello All, We have a requirement to display Initiator IP in ISCSI Configuration Page w= hen Initiator info is enabled for DHCP, find detailed description below. 1. Add an Attempt with Initiator info Enabled for DHCP 2. Save changes 3. On next reboot, Previously added ISCSI attempt will be tried and I= SCSI DHCP server will assign an IP to the client (Initiator IP). 4. It is better to display Initiator IP in same attempt Page like bel= ow Ex:- Initiator IP : 192.168.0.5 // DHCP Process was success Initiator IP : 0.0.0.0 // DHCP process failed Could you please provide your comments to support this feature? Thanks, Karunakar