[edk2] reg: Help on Error Handling
Hello All, We are seeing an issue in HTTPDxe module when there is a hot unplug of a USB Network device while HTTP Post is happening. Details: An application tries to post the data to HTTPS Server using an USB Network device in UEFI environment. When the HTTP Post request Initiated there was a sudden disconnection happening in USB End and In HttpCloseConnection() Exception occurs in HttpInstance->Tcp6->Close . X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 657026F8, CS - 0038, RFLAGS - 00010212 RAX - 62D22E38, RCX - 62D22E38, RDX - 62D22110 RBX - 0007, RSP - 6BDCE0F0, RBP - RSI - 0004, RDI - R8 - 000A, R9 - , R10 - 62D42298 R11 - 6BC48918, R12 - 0004, R13 - R14 - 8003, R15 - 0007 DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 8013, CR2 - , CR3 - 6BC4E000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 65D9D6A0 0047, LDTR - IDTR - 63064018 0FFF, TR - FXSAVE_STATE - 6BDCDD50 Any idea how this case can be handled without exception in the environment where dynamic unplug of a network device which performs UNDI operation. Thanks Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
[edk2] reg: Clarification on PXE Boot with Client and Server in Different Sub nets
Hello, Can you clarify if PXE boot supported to work with Client and PXE / DHCP Server running in different subnet? When the DHCP server running with Relay agent to manage different subnets will PXE boot work? -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
[edk2] reg: Clarification required on ISCSI Initiator Implementation
Hello All, As per the current ISCSI implementation there is only one Initiator name maintained even when there are multiple MAC and attempts are made from an UEFI system. Is there history behind not allowing to change the Initiator Name specific to MAC ? Thanks Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] reg: HTTP Request Failure over Internet
Hello Jiaxin, With the recommended workaround #1 we can able to make HTTP Requests. Thanks Siva -Original Message- From: Wu, Jiaxin [mailto:jiaxin...@intel.com] Sent: Friday, August 10, 2018 7:03 AM To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; edk2-devel@lists.01.org Subject: RE: [edk2] reg: HTTP Request Failure over Internet Hi Siva, Since the gateway and Remote IP is accessible from shell, it means the platform already has the valid gateway, then according the IP policy, it should be ready for the upper layer to access the Internet, UEFI HttpBootDxe driver has verified that by registering one valid gateway. So, the problem is quite possibly in your Http application. My suggestion is that you can check the source code and compare with the logic in the HttpBootDxe driver or you need share the source code to me if possible. Thanks, Jiaxin > -Original Message- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Sivaraman Nainar > Sent: Thursday, August 9, 2018 7:09 PM > To: Wu, Jiaxin ; Ye, Ting ; > Laszlo Ersek ; edk2-devel@lists.01.org > Subject: Re: [edk2] reg: HTTP Request Failure over Internet > > Hello Jiaxin, > > There is no firewall blocking this. The gateway and Remote IP is > accessible from shell. > > Thanks > Siva > -Original Message- > From: Wu, Jiaxin [mailto:jiaxin...@intel.com] > Sent: Monday, August 6, 2018 1:35 PM > To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; edk2-devel@lists.01.org > Subject: RE: [edk2] reg: HTTP Request Failure over Internet > > Is there any proxy or firewall block the connection? Once you set the > static Ip4Gateway via ifconfig shell command, please try to ping the > gateway/remote address to check the connection. > > Thanks, > Jiaxin > > > > -Original Message----- > > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf > > Of Sivaraman Nainar > > Sent: Saturday, August 4, 2018 5:46 PM > > To: Wu, Jiaxin ; Ye, Ting ; > > Laszlo Ersek ; edk2-devel@lists.01.org > > Subject: Re: [edk2] reg: HTTP Request Failure over Internet > > > > Hello Jiaxin, > > > > We have tried both the methods and both failed. Do you have any > > other recommendation? > > > > -Siva > > -Original Message- > > From: Wu, Jiaxin [mailto:jiaxin...@intel.com] > > Sent: Tuesday, July 31, 2018 7:14 AM > > To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; > > edk2-devel@lists.01.org > > Subject: RE: [edk2] reg: HTTP Request Failure over Internet > > > > Hi Siva, > > > > Thanks the report. > > > > From the code review, it does the problem for HTTP protocol to route > > the package over Internet. > > > > But I'm confused with your patch that how can you get the RouterAddr > > since there is no interface for HTTP protocol to get the RouterAddr? > > > > > + HttpInstance->Tcp4->Routes ( > > > +HttpInstance->Tcp4, > > > +FALSE, > > > +>RemoteAddr, > > > +>SubnetMask, > > > +>RouterAddr > > > +); > > > + > > > > So, I prefer it's the UEFI Spec limitation that HTTP protocol > > doesn't provide us the interface to set the router info instead of > > setting it during HTTP configuration. To mitigate the issue, below > > two solution/workaround can be > > tried: > > 1) Ip4Config2 protocol can be leveraged by your HTTP application to > > register one valid Ip4Gateway into the default route table (just > > like HttpBootDxe -- HttpBootRegisterIp4Gateway()). The IP policy > > will route the packet by using the instance's route table first, if > > not found, the default route table will be tried. > > 2) Set the static Ip4Gateway via ifconfig shell command. The > > Ip4Gateway address also will be set to default route table. > > > > Thanks, > > Jiaxin > > > > > > > > > -Original Message- > > > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On > > > Behalf Of Sivaraman Nainar > > > Sent: Wednesday, July 25, 2018 5:29 PM > > > To: Ye, Ting ; Laszlo Ersek > > > ; > > > edk2- de...@lists.01.org > > > Subject: Re: [edk2] reg: HTTP Request Failure over Internet > > > > > > Ting: > > > > > > Please find the patch for reference. > > > > > > Index: HttpProto.c > > > > > > == > > > = > > > --- HttpProto.c > > > +++ HttpProto.c
Re: [edk2] reg: HTTP Request Failure over Internet
Hello Jiaxin,
There is no firewall blocking this. The gateway and Remote IP is accessible
from shell.
Thanks
Siva
-Original Message-
From: Wu, Jiaxin [mailto:jiaxin...@intel.com]
Sent: Monday, August 6, 2018 1:35 PM
To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; edk2-devel@lists.01.org
Subject: RE: [edk2] reg: HTTP Request Failure over Internet
Is there any proxy or firewall block the connection? Once you set the static
Ip4Gateway via ifconfig shell command, please try to ping the gateway/remote
address to check the connection.
Thanks,
Jiaxin
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Sivaraman Nainar
> Sent: Saturday, August 4, 2018 5:46 PM
> To: Wu, Jiaxin ; Ye, Ting ;
> Laszlo Ersek ; edk2-devel@lists.01.org
> Subject: Re: [edk2] reg: HTTP Request Failure over Internet
>
> Hello Jiaxin,
>
> We have tried both the methods and both failed. Do you have any other
> recommendation?
>
> -Siva
> -Original Message-
> From: Wu, Jiaxin [mailto:jiaxin...@intel.com]
> Sent: Tuesday, July 31, 2018 7:14 AM
> To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; edk2-devel@lists.01.org
> Subject: RE: [edk2] reg: HTTP Request Failure over Internet
>
> Hi Siva,
>
> Thanks the report.
>
> From the code review, it does the problem for HTTP protocol to route
> the package over Internet.
>
> But I'm confused with your patch that how can you get the RouterAddr
> since there is no interface for HTTP protocol to get the RouterAddr?
>
> > + HttpInstance->Tcp4->Routes (
> > +HttpInstance->Tcp4,
> > +FALSE,
> > +>RemoteAddr,
> > +>SubnetMask,
> > +>RouterAddr
> > +);
> > +
>
> So, I prefer it's the UEFI Spec limitation that HTTP protocol doesn't
> provide us the interface to set the router info instead of setting it
> during HTTP configuration. To mitigate the issue, below two
> solution/workaround can be
> tried:
> 1) Ip4Config2 protocol can be leveraged by your HTTP application to
> register one valid Ip4Gateway into the default route table (just like
> HttpBootDxe -- HttpBootRegisterIp4Gateway()). The IP policy will route
> the packet by using the instance's route table first, if not found,
> the default route table will be tried.
> 2) Set the static Ip4Gateway via ifconfig shell command. The
> Ip4Gateway address also will be set to default route table.
>
> Thanks,
> Jiaxin
>
>
>
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf
> > Of Sivaraman Nainar
> > Sent: Wednesday, July 25, 2018 5:29 PM
> > To: Ye, Ting ; Laszlo Ersek ;
> > edk2- de...@lists.01.org
> > Subject: Re: [edk2] reg: HTTP Request Failure over Internet
> >
> > Ting:
> >
> > Please find the patch for reference.
> >
> > Index: HttpProto.c
> >
> ==
> > =
> > --- HttpProto.c
> > +++ HttpProto.c
> > @@ -622,12 +622,20 @@
> >Status = HttpInstance->Tcp4->Configure (HttpInstance->Tcp4,
> Tcp4CfgData);
> >if (EFI_ERROR (Status)) {
> > DEBUG ((EFI_D_ERROR, "HttpConfigureTcp4 - %r\n", Status));
> > return Status;
> >}
> >
> > + HttpInstance->Tcp4->Routes (
> > +HttpInstance->Tcp4,
> > +FALSE,
> > +>RemoteAddr,
> > + >SubnetMask,
> > +>RouterAddr
> > +);
> > +
> >Status = HttpCreateTcp4ConnCloseEvent (HttpInstance);
> >if (EFI_ERROR (Status)) {
> > return Status;
> >}
> >
> >Status = HttpCreateTcp4TxEvent (Wrap);
> >
> > -Siva
> > -Original Message-
> > From: Ye, Ting [mailto:ting...@intel.com]
> > Sent: Wednesday, July 25, 2018 1:36 PM
> > To: Laszlo Ersek; Sivaraman Nainar; edk2-devel@lists.01.org
> > Subject: RE: [edk2] reg: HTTP Request Failure over Internet
> >
> > Hi Siva,
> >
> > I didn't receive your patch either. Thanks for reporting the issue,
> > we will try to reproduce it firstly.
> >
> > Thanks,
> > Ting
> >
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf
> > Of Laszlo Ersek
> > Sent: Tuesday, July 24, 2018 8:43 PM
> > To: Sivaraman Nainar ;
> > edk2-devel@lists.01.org
> > Subject: Re: [edk2] reg: HTTP Request Failure over Internet
> >
> > On 07/24/18 14:05, Siva
Re: [edk2] reg: HTTP Request Failure over Internet
Hello Jiaxin,
We have tried both the methods and both failed. Do you have any other
recommendation?
-Siva
-Original Message-
From: Wu, Jiaxin [mailto:jiaxin...@intel.com]
Sent: Tuesday, July 31, 2018 7:14 AM
To: Sivaraman Nainar; Ye, Ting; Laszlo Ersek; edk2-devel@lists.01.org
Subject: RE: [edk2] reg: HTTP Request Failure over Internet
Hi Siva,
Thanks the report.
>From the code review, it does the problem for HTTP protocol to route the
>package over Internet.
But I'm confused with your patch that how can you get the RouterAddr since
there is no interface for HTTP protocol to get the RouterAddr?
> + HttpInstance->Tcp4->Routes (
> +HttpInstance->Tcp4,
> +FALSE,
> +>RemoteAddr,
> +>SubnetMask,
> +>RouterAddr
> +);
> +
So, I prefer it's the UEFI Spec limitation that HTTP protocol doesn't provide
us the interface to set the router info instead of setting it during HTTP
configuration. To mitigate the issue, below two solution/workaround can be
tried:
1) Ip4Config2 protocol can be leveraged by your HTTP application to register
one valid Ip4Gateway into the default route table (just like HttpBootDxe --
HttpBootRegisterIp4Gateway()). The IP policy will route the packet by using the
instance's route table first, if not found, the default route table will be
tried.
2) Set the static Ip4Gateway via ifconfig shell command. The Ip4Gateway address
also will be set to default route table.
Thanks,
Jiaxin
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Sivaraman Nainar
> Sent: Wednesday, July 25, 2018 5:29 PM
> To: Ye, Ting ; Laszlo Ersek ;
> edk2- de...@lists.01.org
> Subject: Re: [edk2] reg: HTTP Request Failure over Internet
>
> Ting:
>
> Please find the patch for reference.
>
> Index: HttpProto.c
> ==
> =
> --- HttpProto.c
> +++ HttpProto.c
> @@ -622,12 +622,20 @@
>Status = HttpInstance->Tcp4->Configure (HttpInstance->Tcp4, Tcp4CfgData);
>if (EFI_ERROR (Status)) {
> DEBUG ((EFI_D_ERROR, "HttpConfigureTcp4 - %r\n", Status));
> return Status;
>}
>
> + HttpInstance->Tcp4->Routes (
> +HttpInstance->Tcp4,
> +FALSE,
> +>RemoteAddr,
> +>SubnetMask,
> +>RouterAddr
> +);
> +
>Status = HttpCreateTcp4ConnCloseEvent (HttpInstance);
>if (EFI_ERROR (Status)) {
> return Status;
>}
>
>Status = HttpCreateTcp4TxEvent (Wrap);
>
> -Siva
> -Original Message-
> From: Ye, Ting [mailto:ting...@intel.com]
> Sent: Wednesday, July 25, 2018 1:36 PM
> To: Laszlo Ersek; Sivaraman Nainar; edk2-devel@lists.01.org
> Subject: RE: [edk2] reg: HTTP Request Failure over Internet
>
> Hi Siva,
>
> I didn't receive your patch either. Thanks for reporting the issue, we
> will try to reproduce it firstly.
>
> Thanks,
> Ting
>
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Laszlo Ersek
> Sent: Tuesday, July 24, 2018 8:43 PM
> To: Sivaraman Nainar ;
> edk2-devel@lists.01.org
> Subject: Re: [edk2] reg: HTTP Request Failure over Internet
>
> On 07/24/18 14:05, Sivaraman Nainar wrote:
> > Hello all,
> >
> > When an application tried to download the remote file over internet
> > with
> the HTTP Get Request it getting failed. If we try via the Intranet
> then application downloads the target file.
> >
> > The remote file is available in the Apache server. With the attached
> > patch
> the download works fine in Internet and Intranet.
> >
> > Could you review the solution and feedback?
>
> The edk2-devel list software does not reflect attachments to subscribers.
>
> While I disagree with that practice in general -- it breaks
> conversations where people justifiedly post small attachments, such as
> PNG screenshots, compressed log files and such --, for posting patches
> specifically, please use git-format-patch and git-send-email. The
> patch should be in the body of the email (please do not copy the
> patch though; that is guaranteed not to work -- please use the git tools).
>
> Official guidelines:
>
> https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Developme
> nt-
> Process
>
> Personal ones from yours truly:
>
> https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt
> -git- guide-for-edk2-contributors-and-maintainers
>
> Thanks,
> Laszlo
> ___
> 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
Re: [edk2] reg: HTTP Request Failure over Internet
Ting:
Please find the patch for reference.
Index: HttpProto.c
===
--- HttpProto.c
+++ HttpProto.c
@@ -622,12 +622,20 @@
Status = HttpInstance->Tcp4->Configure (HttpInstance->Tcp4, Tcp4CfgData);
if (EFI_ERROR (Status)) {
DEBUG ((EFI_D_ERROR, "HttpConfigureTcp4 - %r\n", Status));
return Status;
}
+ HttpInstance->Tcp4->Routes (
+HttpInstance->Tcp4,
+FALSE,
+>RemoteAddr,
+>SubnetMask,
+>RouterAddr
+);
+
Status = HttpCreateTcp4ConnCloseEvent (HttpInstance);
if (EFI_ERROR (Status)) {
return Status;
}
Status = HttpCreateTcp4TxEvent (Wrap);
-Siva
-Original Message-
From: Ye, Ting [mailto:ting...@intel.com]
Sent: Wednesday, July 25, 2018 1:36 PM
To: Laszlo Ersek; Sivaraman Nainar; edk2-devel@lists.01.org
Subject: RE: [edk2] reg: HTTP Request Failure over Internet
Hi Siva,
I didn't receive your patch either. Thanks for reporting the issue, we will try
to reproduce it firstly.
Thanks,
Ting
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Laszlo
Ersek
Sent: Tuesday, July 24, 2018 8:43 PM
To: Sivaraman Nainar ; edk2-devel@lists.01.org
Subject: Re: [edk2] reg: HTTP Request Failure over Internet
On 07/24/18 14:05, Sivaraman Nainar wrote:
> Hello all,
>
> When an application tried to download the remote file over internet with the
> HTTP Get Request it getting failed. If we try via the Intranet then
> application downloads the target file.
>
> The remote file is available in the Apache server. With the attached patch
> the download works fine in Internet and Intranet.
>
> Could you review the solution and feedback?
The edk2-devel list software does not reflect attachments to subscribers.
While I disagree with that practice in general -- it breaks conversations where
people justifiedly post small attachments, such as PNG screenshots, compressed
log files and such --, for posting patches specifically, please use
git-format-patch and git-send-email. The patch should be in the body of the
email (please do not copy the patch though; that is guaranteed not to
work -- please use the git tools).
Official guidelines:
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
Personal ones from yours truly:
https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers
Thanks,
Laszlo
___
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] reg: HTTP Request Failure over Internet
Hello all, When an application tried to download the remote file over internet with the HTTP Get Request it getting failed. If we try via the Intranet then application downloads the target file. The remote file is available in the Apache server. With the attached patch the download works fine in Internet and Intranet. Could you review the solution and feedback? -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] reg: IP6 based Static IP Configuration in ISCSI
Hello Ting, The said behavior is there in IP4 Static IP based ISCSI Connection. The request we are raising here is Setup options to provide IP details and preserve the same. -Siva -Original Message- From: Ye, Ting [mailto:ting...@intel.com] 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 address of iSCSI target according to polices defined in RFC. If the IPv6 address of iSCSI target is not changed, the same IPv6 source address will be chosen under the same policy. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 connection using we can't preserve the IP settings in NVRam as we do in IP4 case right. In order to support that can we have setup questions as same as IP4 which will address this? -Siva -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 IP6 Static IP bases ISCSI connection. Thanks for your detailed clarification. -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 initiator. But it does not mean iSCSI initiator cannot use existing IPv6 address which is previously configured by using "ifconfig6" in Shell. You may have a try. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 disabled. Right? suppressif ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_IP6 OR ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_AUTOCONFIG; -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 address. Just NOT click the checkbox of "Enable DHCP". Thanks, Ting -Original Message----- From: Sivaraman Nainar [mailto:sivaram...@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 Target with Static Addresses. But if we choose the IP6 mode by default no setup options available to choose static and it take DHCP as default. In this case even if we configure IP6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -Original Message- From: Ye, Ting [mailto:ting...@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 iSCSI. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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
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 connection using we can't preserve the IP settings in NVRam as we do in IP4 case right. In order to support that can we have setup questions as same as IP4 which will address this? -Siva -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 IP6 Static IP bases ISCSI connection. Thanks for your detailed clarification. -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 initiator. But it does not mean iSCSI initiator cannot use existing IPv6 address which is previously configured by using "ifconfig6" in Shell. You may have a try. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 disabled. Right? suppressif ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_IP6 OR ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_AUTOCONFIG; -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 address. Just NOT click the checkbox of "Enable DHCP". Thanks, Ting -Original Message----- From: Sivaraman Nainar [mailto:sivaram...@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 Target with Static Addresses. But if we choose the IP6 mode by default no setup options available to choose static and it take DHCP as default. In this case even if we configure IP6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -Original Message- From: Ye, Ting [mailto:ting...@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 iSCSI. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you. ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
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 IP6 Static IP bases ISCSI connection. Thanks for your detailed clarification. -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 initiator. But it does not mean iSCSI initiator cannot use existing IPv6 address which is previously configured by using "ifconfig6" in Shell. You may have a try. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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 disabled. Right? suppressif ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_IP6 OR ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_AUTOCONFIG; -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 address. Just NOT click the checkbox of "Enable DHCP". Thanks, Ting -Original Message----- From: Sivaraman Nainar [mailto:sivaram...@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 Target with Static Addresses. But if we choose the IP6 mode by default no setup options available to choose static and it take DHCP as default. In this case even if we configure IP6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -Original Message- From: Ye, Ting [mailto:ting...@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 iSCSI. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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
[edk2] reg: PXE Boot Enhancement
Hello All, During PXE boot if the operation fails to connect the PXE server, system waits for the user's manual Key input to abort the operation and proceed further. It would be nice to have an option to set timeout before starting PXE boot so that if there's any issue with the PXE boot process, the system can automatically abort the boot and proceed to next boot after the specified time. Could you please feedback on this. -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
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 disabled. Right? suppressif ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_IP6 OR ideqval ISCSI_CONFIG_IFR_NVDATA.IpMode == IP_MODE_AUTOCONFIG; -Siva -Original Message- From: Ye, Ting [mailto:ting...@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 address. Just NOT click the checkbox of "Enable DHCP". Thanks, Ting -Original Message----- From: Sivaraman Nainar [mailto:sivaram...@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 Target with Static Addresses. But if we choose the IP6 mode by default no setup options available to choose static and it take DHCP as default. In this case even if we configure IP6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -Original Message- From: Ye, Ting [mailto:ting...@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 iSCSI. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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
Re: [edk2] 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 Target with Static Addresses. But if we choose the IP6 mode by default no setup options available to choose static and it take DHCP as default. In this case even if we configure IP6 using IfConfig6, it will override by ISCSI. Is my understanding correct? Thanks Siva -Original Message- From: Ye, Ting [mailto:ting...@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 iSCSI. Thanks, Ting -Original Message- From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sivaraman 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] 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
Re: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table
Hello Ting,
Yes. In the use case we said:
NIC 1 - Target 1 : Login success
NIC 1 - Target 2 : Login success
NIC 2 - Target 1 : Login success
But iSCSI Driver will choose the first login session and abort the other in the
same NIC. But even it is aborted it is Published to IBFT.
As you said the ESXi and SLES not able to proceed installation assuming more
than one IBFT for the same NIC as illegal.
So what the clarification we are asking is since it's an aborted attempt can we
skip adding IBFT entry for the aborted attempt.
Please refer the ticket already created for this has the proposed solution.
https://bugzilla.tianocore.org/show_bug.cgi?id=968
-Siva
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Ye, Ting
Sent: Wednesday, June 06, 2018 2:04 PM
To: Omkar K; edk2-devel@lists.01.org
Cc: Madhan B. Santharam
Subject: Re: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table
Hi Omkar,
If not MPIO, current iSCSI driver will try the configured attempts and only
publish the successful entries in iBFT. The failed attempts will be removed.
In your case, it looks the ESXi and SLES OS treat the multiple entries on one
NIC (different targets) are illegal.
Thanks,
Ting
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Omkar K
Sent: Tuesday, June 5, 2018 5:01 PM
To: Ye, Ting ; edk2-devel@lists.01.org
Cc: Madhan B. Santharam
Subject: Re: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table
Hello Ting,
1. We did not enable MPIO.
2. in IScsiStart(), at this point
//
// Select the first login session. Abort others.
//
if (Private->Session == NULL) {
Private->Session = Session;
BootSelected = AttemptConfigData->AttemptConfigIndex;
//
// Don't validate other attempt in multipath mode if one is success.
//
if (mPrivate->EnableMpio) {
break;
}
} else {
IScsiSessionAbort (Session);
FreePool (Session);
}
other than one attempt per Nic, other sessions are aborted. Still, all the
attempts are published in IBFT.
We can observe the issue when different targets are configured on one NIC where
all the attempts are published in IBFT.
But, the issue disappeared when the aborted attempts are not published in IBFT.
Thanks,
Omkar
-Original Message-
From: Ye, Ting [mailto:ting...@intel.com]
Sent: Monday, June 04, 2018 2:26 PM
To: Sivaraman Nainar; edk2-devel@lists.01.org
Cc: Omkar K; Madhan B. Santharam
Subject: RE: reg: ISCSI Aborted attempt entry in IBFT Table
Hi Siva,
Per design, the iSCSI multipath I/O will publish all configured attempts to
IBFT, no matter the connection is success or fail currently.
Did you enable the MPIO when you configure the attempts?
I am not clear what do you mean "aborted attempt".
Thanks,
Ting
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
Sivaraman Nainar
Sent: Thursday, May 31, 2018 8:18 PM
To: edk2-devel@lists.01.org
Cc: Omkar K ; Madhan B. Santharam
Subject: [edk2] reg: ISCSI Aborted attempt entry in IBFT Table
Hello all:
Here is the issue which requires clarification.
Issue Synopsis:
When there are more than one iSCSI target configured and Ibft table published
with the connected and aborted attempt details, all the targets are not seen in
ESXi and SLES OS. But in Windows it can see the targets connected.
Use case:
Target 1: IP : 192.xx.xx.31 Target 2 : IP : 192.xx.xx.1
NIC 1 configured with attempts Target 1 & Target 2 NIC 2 configured with
attempts Target 1 Connection
Login
Ibft
Block Device in UEFI Shell
SLES / Esx OS
Windows
NIC1 Target1
Success
Published
Mounted
Target Seen
NIC1 Target2
Success
Published
Mounted
Target Seen
NIC1 Target1
NIC1 Target2
NIC2 Target1
Individual Login success
Published for all attempts (3)
NIC1 Target 1 NIC2 Target 1
None Seen
NIC1 Target 1 NIC2 Target 1
When the attempts which are login success but Aborted by ISCSI Driver are
present in ibft table SLES and ESX not able to see the targets during
Installation.
If the ISCSI Driver not adding the ibft entry for the aborted attempts then the
targets are seen in Esx and SLES.
So it requires clarification that If the driver need to SKIP adding the aborted
attempt entry to ibft or its OS responsibility to handle the invalid entries in
ibft.
-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
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lis
[edk2] reg: ISCSI Aborted attempt entry in IBFT Table
Hello all: Here is the issue which requires clarification. Issue Synopsis: When there are more than one iSCSI target configured and Ibft table published with the connected and aborted attempt details, all the targets are not seen in ESXi and SLES OS. But in Windows it can see the targets connected. Use case: Target 1: IP : 192.xx.xx.31 Target 2 : IP : 192.xx.xx.1 NIC 1 configured with attempts Target 1 & Target 2 NIC 2 configured with attempts Target 1 Connection Login Ibft Block Device in UEFI Shell SLES / Esx OS Windows NIC1 Target1 Success Published Mounted Target Seen NIC1 Target2 Success Published Mounted Target Seen NIC1 Target1 NIC1 Target2 NIC2 Target1 Individual Login success Published for all attempts (3) NIC1 Target 1 NIC2 Target 1 None Seen NIC1 Target 1 NIC2 Target 1 When the attempts which are login success but Aborted by ISCSI Driver are present in ibft table SLES and ESX not able to see the targets during Installation. If the ISCSI Driver not adding the ibft entry for the aborted attempts then the targets are seen in Esx and SLES. So it requires clarification that If the driver need to SKIP adding the aborted attempt entry to ibft or its OS responsibility to handle the invalid entries in ibft. -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] reg: EDK2 - HTTP Boot Image Validation
Hello Fu Siyuan, We can skip the header check if we know the image type. That should be enough. -Siva -Original Message- From: Fu, Siyuan [mailto:siyuan...@intel.com] Sent: Wednesday, May 23, 2018 11:14 AM To: Sivaraman Nainar; edk2-devel@lists.01.org Subject: RE: reg: EDK2 - HTTP Boot Image Validation Hi, Siva What do you mean by "skip the validation of image types"? Do you want to skip the "Content-type" HTTP header check, or name extension check, or both of them? BestRegards Fu Siyuan > -Original Message- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Sivaraman Nainar > Sent: Friday, May 18, 2018 5:17 PM > To: edk2-devel@lists.01.org > Subject: [edk2] reg: EDK2 - HTTP Boot Image Validation > > Hello all, > When HTTP Boot performed the code checking if the Image type as EFI > ISO and IMG. If not the boot not when the content type is as > "Content-type: text/plain". > https://github.com/tianocore/edk2/blob/master/NetworkPkg/HttpBootDxe/H > ttpB ootSupport.c (HttpBootCheckImageType()) > > But as per RFC it described below. > https://tools.ietf.org/html/rfc2616#section-7.2.1: > "If and only if the media type is not given by a Content-Type field, > the recipient MAY attempt to guess the media type via inspection of > its content and/or the name extension(s) of the URI used to identify > the resource." > Can you please comment if this need to be addressed such a way we can > skip the validation of image types. > -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] reg: EDK2 - HTTP Boot Image Validation
Hello all, When HTTP Boot performed the code checking if the Image type as EFI ISO and IMG. If not the boot not proceeding when the content type is as "Content-type: text/plain". https://github.com/tianocore/edk2/blob/master/NetworkPkg/HttpBootDxe/HttpBootSupport.c (HttpBootCheckImageType()) But as per RFC it described below. https://tools.ietf.org/html/rfc2616#section-7.2.1: "If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource." Can you please comment if this need to be addressed such a way we can skip the validation of image types. -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
[edk2] reg: EDK2 - HTTP Boot
Hello All, There is an observation found during HTTP Boot that, when HTTP 1.1 server does not support keep-alives, the system sometimes failed boot when connections are not persistent. RFC 2616 section 8.2.1 says "HTTP/1.1 servers SHOULD maintain persistent connections and use TCP's flow control mechanisms to resolve temporary overloads, rather than terminating connections with the expectation that clients will retry. The latter technique can exacerbate network congestion." https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html So the understanding here is Server should not assume or expect that client will retry. Would like to confirm if the EDK II implementation expects the Server should persistent connection. -Siva ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
