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=ting.ye@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 074A821B02845 for ; Mon, 23 Jul 2018 00:36:19 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jul 2018 00:36:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,392,1526367600"; d="scan'208";a="59001645" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga008.jf.intel.com with ESMTP; 23 Jul 2018 00:36:16 -0700 Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 23 Jul 2018 00:36:15 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx109.amr.corp.intel.com (10.18.116.9) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 23 Jul 2018 00:36:15 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.100]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.173]) with mapi id 14.03.0319.002; Mon, 23 Jul 2018 15:36:13 +0800 From: "Ye, Ting" To: Sivaraman Nainar , "edk2-devel@lists.01.org" Thread-Topic: reg: IP6 based Static IP Configuration in ISCSI Thread-Index: AdQSuq98CsmHYPP2Txyk3Yx5Xad3YQAgGPzgAAlJ3AAAAGBi0AAAyT0wAADlRHACWntQAADRDY6QAIxyIUAAA25KkAAALPoA Date: Mon, 23 Jul 2018 07:36:13 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: reg: IP6 based Static IP Configuration in ISCSI X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 07:36:20 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Siva, IPv4 RFCs do not define source address selection but IPv6 RFCs do. Even if = we add setup options for IPv6 source address in iSCSI, it is still up to IP= 6 driver to choose the best matched source address in current implementatio= n. For example, if you set fec0::2001/64 as source address in iSCSI UI, while = the target address is fed0::100/64; and there is another source address fed= 0::1234/64 set by ifconfig6 previously, iSCSI drive will still use fed0::12= 34/64 not the one you configured in iSCSI UI. This is the historical background the UI configuration for IPv6/IPv6 is dif= ferent in iSCSI. Thanks, Ting -----Original Message----- From: Sivaraman Nainar [mailto:sivaramann@amiindia.co.in]=20 Sent: Monday, July 23, 2018 3:25 PM To: Ye, Ting ; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Hello Ting, The said behavior is there in IP4 Static IP based ISCSI Connection. The req= uest we are raising here is Setup options to provide IP details and preserv= e the same. -Siva -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com]=20 Sent: Monday, July 23, 2018 11:20 AM To: Sivaraman Nainar; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Hi Siva, IP6 driver will perform source address selection to best match the IPv6 add= ress of iSCSI target according to polices defined in RFC. If the IPv6 addre= ss of iSCSI target is not changed, the same IPv6 source address will be cho= sen under the same policy. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Siva= raman Nainar Sent: Friday, July 20, 2018 6:46 PM To: Sivaraman Nainar ; Ye, Ting ; edk2-devel@lists.01.org Subject: Re: [edk2] reg: IP6 based Static IP Configuration in ISCSI Hello Ting, We have one more clarification need. When we are doing this way of ISCSI co= nnection using we can't preserve the IP settings in NVRam as we do in IP4 c= ase right. In order to support that can we have setup questions as same as IP4 which w= ill address this? -Siva -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Siva= raman Nainar Sent: Monday, July 16, 2018 1:04 PM To: Ye, Ting; edk2-devel@lists.01.org Subject: Re: [edk2] reg: IP6 based Static IP Configuration in ISCSI Hello Ting, As you recommended with shell based IP assignment we are able to use the IP= 6 Static IP bases ISCSI connection. Thanks for your detailed clarification. -Siva -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com] Sent: Wednesday, July 4, 2018 1:17 PM To: Sivaraman Nainar; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Hi Siva, Yes iSCSI UI does not allow the user to configure static IP address for ini= tiator. But it does not mean iSCSI initiator cannot use existing IPv6 addre= ss which is previously configured by using "ifconfig6" in Shell. You may have a try. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Siva= raman Nainar Sent: Wednesday, July 4, 2018 3:04 PM To: Ye, Ting ; edk2-devel@lists.01.org Subject: Re: [edk2] reg: IP6 based Static IP Configuration in ISCSI Hello Ting, What I am trying to do is setting STATIC IP for Initiator. But as per below= VFR content, when we choose IP6 the controls to accept Static IP will be d= isabled. Right? suppressif ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode =3D=3D IP_MODE_IP6 OR ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode =3D=3D IP_MODE_AUTOCO= NFIG; -Siva -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com] Sent: Wednesday, July 4, 2018 12:12 PM To: Sivaraman Nainar; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Hi Siva, No, it is not correct. In iSCSI UI, if you choose IP6 mode, you still have chance to use static ad= dress. Just NOT click the checkbox of "Enable DHCP". Thanks, Ting -----Original Message----- From: Sivaraman Nainar [mailto:sivaramann@amiindia.co.in] Sent: Wednesday, July 4, 2018 2:32 PM To: Ye, Ting ; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Ting, Let me clarify in detail. When we have IP4 mode selection in ISCSI we can set both Initiator and Targ= et with Static Addresses. But if we choose the IP6 mode by default no setup options available to choo= se static and it take DHCP as default. In this case even if we configure IP= 6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -----Original Message----- From: Ye, Ting [mailto:ting.ye@intel.com] Sent: Wednesday, July 4, 2018 7:37 AM To: Sivaraman Nainar; edk2-devel@lists.01.org Subject: RE: reg: IP6 based Static IP Configuration in ISCSI Hi Siva, We don't have such plan as I known. For IPv6, we leave it to IP6 driver to = perform source address selection to best match the iSCSI target address. You could use ifconfig6 to set static IP6 address before you configure iSCS= I. Thanks, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Siva= raman Nainar Sent: Tuesday, July 3, 2018 6:44 PM To: edk2-devel@lists.01.org Subject: [edk2] reg: IP6 based Static IP Configuration in ISCSI Hello, At present in the ISCSI configuration we are able to specify the Static IP = configuration for IP4 protocol. Is there any plan to support IP6 static IP = configuration in ISCSI Configuration? -Siva _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel This e-mail is intended for the use of the addressee only and may contain p= rivileged, confidential, or proprietary information that is exempt from dis= closure under law. If you have received this message in error, please infor= m us promptly by reply e-mail, then delete the e-mail and destroy any print= ed copy. Thank you. _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel