From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=203.199.198.232; helo=imsva.in.megatrends.com; envelope-from=karunakarp@amiindia.co.in; receiver=edk2-devel@lists.01.org Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (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 64C3A2095B066 for ; Mon, 9 Oct 2017 21:05:34 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3281D8205E; Tue, 10 Oct 2017 09:41:49 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0F1208205B; Tue, 10 Oct 2017 09:41:49 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Tue, 10 Oct 2017 09:41:49 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Tue, 10 Oct 2017 09:38:58 +0530 From: Karunakar P To: "'Wu, Jiaxin'" , "'edk2-devel@lists.01.org'" CC: "Fu, Siyuan" , "Ye, Ting" Thread-Topic: Request to display Initiator IP in ISCSI Attempt Page Thread-Index: AQHTQXCg7NRPhJGnqkevqPWnvJ+GzqLcbLuA Date: Tue, 10 Oct 2017 04:08:57 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B72741633C764@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B72741633C764@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.128] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23382.004 X-TM-AS-Result: No--22.659-5.0-31-10 X-imss-scan-details: No--22.659-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23382.004 X-TMASE-Result: 10--22.659000-10.000000 X-TMASE-MatchedRID: qsaWi0FWcYunykMun0J1wpmug812qIbz9pLnYtQ99xKgOUc+PAfSOyLm 4/WzmuzLc6z2f4iL3P/I4DnS0/bnBKjmA6eZ5vSksyNb+yeIRAohauGyjTkf9Uw6MpTEJnCvjEx Zqwk4Wlf5yPaI4eFKR4rapsNpkVkzX8Yxzpc8wYeVUcz8XpiS9BSRa9qpSosfXCmcAC8DBrOraR WKBb9AMmGgt8kEaiedwOkKOb70pfqjG/WUQM0mIxcqpH7D1rtQU5ulGJaO5WvA0NSRYNJF5v0uc myRbvOGQGLBSmJfxT1JpV9rHFX3j+2u5u3xOQvhwbRQ2Bpmlioay+BQxgCfhZb7No0srrTk7KBB Z2QBUyzQ23n+P5pIMRQjizXtCXfTWYqLLUX2mAtB6yOrxc8xu3cF/0kiqyh4RtqpRW8sWyJqRyr ZEAcpymPqdi9REDedf7I+P8ORpcmc0H8AUS5IGRz2MDiYujy5pfVcx39Kq+4QHQ+7AkbTsZm3Ck ZsyRGFwmm5gw944w+6rmzU3nJhUA5VocU4CFzq2x/FmlC/aoy08Z6Wwo67iLjV6s6mdtCJYyzka Ncuq8ZWZo3G/TpFVQAWZv/M6/wIo27w8ee4WC9jiC4p+/AIFqB+8dFYucCesstO9qYbwEmjxYyR Ba/qJeBPbNdhr3+dPerMcoCGxRggBwKKRHe+rxuiOUZbDkiKmMHj44xU0O03VJfEKydgsRy6Wl+ AU/8tB9ey7jgRzN4= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-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 04:05:35 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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