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 8C60721F3C1B9 for ; Tue, 10 Oct 2017 00:16:05 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Oct 2017 00:19:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,503,1500966000"; d="scan'208,217";a="144718538" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga002.jf.intel.com with ESMTP; 10 Oct 2017 00:19:32 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 10 Oct 2017 00:19:31 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.98]) with mapi id 14.03.0319.002; Tue, 10 Oct 2017 15:19:29 +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//+YQoD//2iMAA== Date: Tue, 10 Oct 2017 07:19:29 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B72741633C99A@SHSMSX103.ccr.corp.intel.com> References: <895558F6EA4E3B41AC93A00D163B72741633C764@SHSMSX103.ccr.corp.intel.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2VkYzdkNTItMzBmMC00ZjY2LWI4ZmUtMTk1NzcwY2ZlYmU1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Ikp6Z0ZYY1AxVWx5VHZHRWFhTEtyQlY1bmdiZjZaRksyWVo0dEgzR1wvdFJzPSJ9 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 07:16:05 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Karunakar, Unlike IPv4, IPv6 address used for iSCSI session can always be retrieved ma= nually. Since we expect the user configure the IPv6 address manually, I don= 't prefer adding the Initiator IP In IP6 attempt Page because the user shou= ld have known it as setting in step1. Thanks, Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Tuesday, October 10, 2017 12:09 PM To: Wu, Jiaxin ; 'edk2-devel@lists.01.org' Cc: Fu, Siyuan ; Ye, Ting Subject: RE: Request to display Initiator IP in ISCSI Attempt Page Hi Jiaxin, Thanks for your support. I've created a ticket in Bugzilla, and below are the details https://bugzilla.tianocore.org/show_bug.cgi?id=3D732 Yeah we should grayout the Initiator info to indicate it's un-configurable= . In case of IPv6 1. Before trying for ISCSI connection(with IPv6 attempt), we'll confi= gure the IP manually. 2. While trying for ISCSI Connection(with IPv6 attempt), It may use t= he above Configured IP or link local address. 3. Can we display the whatever IP used for ISCSI connection(with IPv6= attempt) as Initiator IP In IP6 attempt Page? , So that we can know what I= nitiator IP used for ISCSI connection. Could you please let me know if anything is wrong. Thanks, Karunakar From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] Sent: Tuesday, October 10, 2017 8:07 AM To: Karunakar P; 'edk2-devel@lists.01.org' Cc: Fu, Siyuan; Ye, Ting Subject: RE: Request to display Initiator IP in ISCSI Attempt Page 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, Jiaxi= n >; 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