NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed

* NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
@ 2021-06-23 21:08 Bret Barkelew
  2021-06-25  7:25 ` [edk2-devel] " brbarkel
  0 siblings, 1 reply; 13+ messages in thread
From: Bret Barkelew @ 2021-06-23 21:08 UTC (permalink / raw)
  To: devel@edk2.groups.io, LathaKannan Arumugam,
	'maciej.rabeda@linux.intel.com', Jiaxin Wu, Siyuan Fu

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Hi all!

Trying to track down an unexpected behavior for one of our teams here:
“We tried to PXEBoot a VM using IPv6 and even though the server replied with all requested boot options, the firmware for some reason did a DHCPv6 release instead of going for a network boot.”

The team dug in with some debugging and tracked things down to this process and the associated code:

  1.  DHCP server is sending REPLY with valid boot params and tftp server address.
  2.  UEFI upon receiving this REPLY, it is trying to send UDP request with port 4011 and uses TFTP global address as destination address.
  3.  Ip6Output() in /NetworkPkg/Ip6Dxe/Ip6Output.c drops the UDP request generated in Step-2. This is due to route miss.
     *   Function: https://github.com/tianocore/edk2/blob/20ca52882877ba9025da2ee58c8dab7808eca457/NetworkPkg/Ip6Dxe/Ip6Output.c#L476
     *   Error return: https://github.com/tianocore/edk2/blob/20ca52882877ba9025da2ee58c8dab7808eca457/NetworkPkg/Ip6Dxe/Ip6Output.c#L701
  4.  As the UDP request with port 4011 failed, UEFI does a RELEASE message and errors out.
  5.  Below the code snippet inside UEFI where packet is getting dropped.

Here’s some questions from the team:

  1.  Why is UEFI doing UDP request with port 4011 to TFTP server address. We expect it to start TFTP with data provided in REPLY by server.
  2.  In data center, the blades are not directly connected to server. So how can UEFI learn the routes to send a unicast request using global address.
  3.  In case of IPv4, we don’t see any UDP request using port 4011. Why alone for IPv6?


Thoughts? Thanks in advance!

- Bret


[-- Attachment #2: Type: text/html, Size: 8077 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-23 21:08 NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6 Bret Barkelew
@ 2021-06-25  7:25 ` brbarkel
  2021-06-25 14:40   ` Maciej Rabeda
  0 siblings, 1 reply; 13+ messages in thread
From: brbarkel @ 2021-06-25  7:25 UTC (permalink / raw)
  To: Bret Barkelew, devel

[-- Attachment #1: Type: text/plain, Size: 58 bytes --]

Just poking this to see if anyone has any ideas. Thanks!

[-- Attachment #2: Type: text/html, Size: 58 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-25  7:25 ` [edk2-devel] " brbarkel
@ 2021-06-25 14:40   ` Maciej Rabeda
  2021-06-25 16:19     ` [EXTERNAL] " Bret Barkelew
  0 siblings, 1 reply; 13+ messages in thread
From: Maciej Rabeda @ 2021-06-25 14:40 UTC (permalink / raw)
  To: devel, brbarkel, Bret Barkelew

[-- Attachment #1: Type: text/plain, Size: 182 bytes --]

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:
> Just poking this to see if anyone has any ideas. Thanks!
> 


[-- Attachment #2: Type: text/html, Size: 567 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-25 14:40   ` Maciej Rabeda
@ 2021-06-25 16:19     ` Bret Barkelew
  2021-06-25 16:22       ` larumugam
  0 siblings, 1 reply; 13+ messages in thread
From: Bret Barkelew @ 2021-06-25 16:19 UTC (permalink / raw)
  To: Rabeda, Maciej, devel@edk2.groups.io, LathaKannan Arumugam

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; Bret Barkelew <Bret.Barkelew@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:
Just poking this to see if anyone has any ideas. Thanks!



[-- Attachment #2: Type: text/html, Size: 1376 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-25 16:19     ` [EXTERNAL] " Bret Barkelew
@ 2021-06-25 16:22       ` larumugam
  2021-06-25 20:11         ` LathaKannan Arumugam
       [not found]         ` <168BEC4CE79D1C8A.1293@groups.io>
  0 siblings, 2 replies; 13+ messages in thread
From: larumugam @ 2021-06-25 16:22 UTC (permalink / raw)
  To: Bret Barkelew, Rabeda, Maciej, devel@edk2.groups.io


[-- Attachment #1.1: Type: text/plain, Size: 1153 bytes --]

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io; LathaKannan Arumugam <larumugam@microsoft.com>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?
On 25-Jun-21 09:25, brbarkel via groups.io wrote:
Just poking this to see if anyone has any ideas. Thanks!



[-- Attachment #1.2: Type: text/html, Size: 4301 bytes --]

[-- Attachment #2: DHCPv6_Server.cap --]
[-- Type: image/cap, Size: 3508 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-25 16:22       ` larumugam
@ 2021-06-25 20:11         ` LathaKannan Arumugam
       [not found]         ` <168BEC4CE79D1C8A.1293@groups.io>
  1 sibling, 0 replies; 13+ messages in thread
From: LathaKannan Arumugam @ 2021-06-25 20:11 UTC (permalink / raw)
  To: Bret Barkelew, Rabeda, Maciej, devel@edk2.groups.io

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

Any inputs?
We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.


From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?
On 25-Jun-21 09:25, brbarkel via groups.io wrote:
Just poking this to see if anyone has any ideas. Thanks!



[-- Attachment #2: Type: text/html, Size: 5302 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

[parent not found: <168BEC4CE79D1C8A.1293@groups.io>]

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
       [not found]         ` <168BEC4CE79D1C8A.1293@groups.io>
@ 2021-06-28 20:05           ` LathaKannan Arumugam
  2021-06-29 16:36             ` Maciej Rabeda
       [not found]             ` <168D1AEBDC669830.32494@groups.io>
  0 siblings, 2 replies; 13+ messages in thread
From: LathaKannan Arumugam @ 2021-06-28 20:05 UTC (permalink / raw)
  To: devel@edk2.groups.io, Bret Barkelew, Rabeda, Maciej

[-- Attachment #1: Type: text/plain, Size: 2294 bytes --]

Can you please help us on this issues?
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: devel@edk2.groups.io <devel@edk2.groups.io> on behalf of LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io>
Sent: Friday, June 25, 2021 1:11:42 PM
To: Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io <devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6


Any inputs?

We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.





From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6



Attached packet captured from server.



From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6



+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>



- Bret

________________________________

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6



Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:

Just poking this to see if anyone has any ideas. Thanks!





[-- Attachment #2: Type: text/html, Size: 5165 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-28 20:05           ` LathaKannan Arumugam
@ 2021-06-29 16:36             ` Maciej Rabeda
       [not found]             ` <168D1AEBDC669830.32494@groups.io>
  1 sibling, 0 replies; 13+ messages in thread
From: Maciej Rabeda @ 2021-06-29 16:36 UTC (permalink / raw)
  To: devel, larumugam, Bret Barkelew

[-- Attachment #1: Type: text/plain, Size: 3262 bytes --]

Hi guys,

Finally got some time to look into it.

Long story short, this smells like infrastructure problem.
SARR passes over 546/547 port pair. That is between UEFI PXE client and 
DHCP server (even if it is the same machine).
The next packet is essentially a Boot Server choice step. UEFI PXE 
client sends a unicast discovery packet towards Boot server (same 
machine, same address) coded as DHCP Request.
The release packet is a direct reaction to 3 second timeout (see time 
diff between packet 9 and 11).

See section 2.2.1 in PXE spec: 
http://www.pix.net/software/pxeboot/archive/pxespec.pdf

Please verify that your WDS service is running correctly, since clearly 
there is no reaction to that packet from Boot server.



On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
> Can you please help us on this issues?
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* devel@edk2.groups.io <devel@edk2.groups.io> on behalf of 
> LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io>
> *Sent:* Friday, June 25, 2021 1:11:42 PM
> *To:* Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej 
> <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io 
> <devel@edk2.groups.io>
> *Subject:* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP 
> RELEASE after PXE server reply on IPv6
>
> Any inputs?
>
> We kind of blocked on this for a week. Kindly look into packet capture 
> and suggest a path forward.
>
> *From:* LathaKannan Arumugam
> *Sent:* Friday, June 25, 2021 9:23 AM
> *To:* Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej 
> <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io
> *Subject:* RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP 
> RELEASE after PXE server reply on IPv6
>
> Attached packet captured from server.
>
> *From:* Bret Barkelew <Bret.Barkelew@microsoft.com 
> <mailto:Bret.Barkelew@microsoft.com>>
> *Sent:* Friday, June 25, 2021 9:19 AM
> *To:* Rabeda, Maciej <maciej.rabeda@linux.intel.com 
> <mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io 
> <mailto:devel@edk2.groups.io>; LathaKannan Arumugam 
> <larumugam@microsoft.com <mailto:larumugam@microsoft.com>>
> *Subject:* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP 
> RELEASE after PXE server reply on IPv6
>
> + @LathaKannan Arumugam <mailto:larumugam@microsoft.com>
>
> - Bret
>
> ------------------------------------------------------------------------
>
> *From:*Rabeda, Maciej <maciej.rabeda@linux.intel.com 
> <mailto:maciej.rabeda@linux.intel.com>>
> *Sent:* Friday, June 25, 2021 7:40:16 AM
> *To:* devel@edk2.groups.io <mailto:devel@edk2.groups.io> 
> <devel@edk2.groups.io <mailto:devel@edk2.groups.io>>; Bret Barkelew 
> <Bret.Barkelew@microsoft.com <mailto:Bret.Barkelew@microsoft.com>>; 
> Bret Barkelew <Bret.Barkelew@microsoft.com 
> <mailto:Bret.Barkelew@microsoft.com>>
> *Subject:* [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP 
> RELEASE after PXE server reply on IPv6
>
> Looking at it. Any chance to get Wireshark trace for this scenario?
>
> On 25-Jun-21 09:25, brbarkel via groups.io wrote:
>
>     Just poking this to see if anyone has any ideas. Thanks!
>
> 


[-- Attachment #2.1: Type: text/html, Size: 9107 bytes --]

[-- Attachment #2.2: knjfchcdfhflfima.png --]
[-- Type: image/png, Size: 69408 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

[parent not found: <168D1AEBDC669830.32494@groups.io>]

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
       [not found]             ` <168D1AEBDC669830.32494@groups.io>
@ 2021-06-29 16:39               ` Maciej Rabeda
  2021-06-29 16:53                 ` Bret Barkelew
  0 siblings, 1 reply; 13+ messages in thread
From: Maciej Rabeda @ 2021-06-29 16:39 UTC (permalink / raw)
  To: devel, larumugam, Bret Barkelew

[-- Attachment #1: Type: text/plain, Size: 3502 bytes --]

Additionally, for claim that IPv4 does not do that, please provide 
Wireshark trace, if available.

On 29-Jun-21 18:36, Maciej Rabeda wrote:
> Hi guys,
>
> Finally got some time to look into it.
>
> Long story short, this smells like infrastructure problem.
> SARR passes over 546/547 port pair. That is between UEFI PXE client 
> and DHCP server (even if it is the same machine).
> The next packet is essentially a Boot Server choice step. UEFI PXE 
> client sends a unicast discovery packet towards Boot server (same 
> machine, same address) coded as DHCP Request.
> The release packet is a direct reaction to 3 second timeout (see time 
> diff between packet 9 and 11).
>
> See section 2.2.1 in PXE spec: 
> http://www.pix.net/software/pxeboot/archive/pxespec.pdf
>
> Please verify that your WDS service is running correctly, since 
> clearly there is no reaction to that packet from Boot server.
>
>
>
> On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
>> Can you please help us on this issues?
>> Get Outlook for Android <https://aka.ms/AAb9ysg>
>> ------------------------------------------------------------------------
>> *From:* devel@edk2.groups.io <devel@edk2.groups.io> on behalf of 
>> LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io>
>> *Sent:* Friday, June 25, 2021 1:11:42 PM
>> *To:* Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej 
>> <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io 
>> <devel@edk2.groups.io>
>> *Subject:* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected 
>> DHCP RELEASE after PXE server reply on IPv6
>>
>> Any inputs?
>>
>> We kind of blocked on this for a week.  Kindly look into packet 
>> capture and suggest a path forward.
>>
>> *From:* LathaKannan Arumugam
>> *Sent:* Friday, June 25, 2021 9:23 AM
>> *To:* Bret Barkelew <Bret.Barkelew@microsoft.com>; Rabeda, Maciej 
>> <maciej.rabeda@linux.intel.com>; devel@edk2.groups.io
>> *Subject:* RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected 
>> DHCP RELEASE after PXE server reply on IPv6
>>
>> Attached packet captured from server.
>>
>> *From:* Bret Barkelew <Bret.Barkelew@microsoft.com 
>> <mailto:Bret.Barkelew@microsoft.com>>
>> *Sent:* Friday, June 25, 2021 9:19 AM
>> *To:* Rabeda, Maciej <maciej.rabeda@linux.intel.com 
>> <mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io 
>> <mailto:devel@edk2.groups.io>; LathaKannan Arumugam 
>> <larumugam@microsoft.com <mailto:larumugam@microsoft.com>>
>> *Subject:* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected 
>> DHCP RELEASE after PXE server reply on IPv6
>>
>> + @LathaKannan Arumugam <mailto:larumugam@microsoft.com>
>>
>> - Bret
>>
>> ------------------------------------------------------------------------
>>
>> *From:*Rabeda, Maciej <maciej.rabeda@linux.intel.com 
>> <mailto:maciej.rabeda@linux.intel.com>>
>> *Sent:* Friday, June 25, 2021 7:40:16 AM
>> *To:* devel@edk2.groups.io <mailto:devel@edk2.groups.io> 
>> <devel@edk2.groups.io <mailto:devel@edk2.groups.io>>; Bret Barkelew 
>> <Bret.Barkelew@microsoft.com <mailto:Bret.Barkelew@microsoft.com>>; 
>> Bret Barkelew <Bret.Barkelew@microsoft.com 
>> <mailto:Bret.Barkelew@microsoft.com>>
>> *Subject:* [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP 
>> RELEASE after PXE server reply on IPv6
>>
>> Looking at it. Any chance to get Wireshark trace for this scenario?
>>
>> On 25-Jun-21 09:25, brbarkel via groups.io wrote:
>>
>>     Just poking this to see if anyone has any ideas. Thanks!
>>
>
> 


[-- Attachment #2.1: Type: text/html, Size: 10392 bytes --]

[-- Attachment #2.2: knjfchcdfhflfima.png --]
[-- Type: image/png, Size: 69408 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-29 16:39               ` Maciej Rabeda
@ 2021-06-29 16:53                 ` Bret Barkelew
  2021-06-29 17:33                   ` Vincent Zimmer
  0 siblings, 1 reply; 13+ messages in thread
From: Bret Barkelew @ 2021-06-29 16:53 UTC (permalink / raw)
  To: devel@edk2.groups.io, maciej.rabeda@linux.intel.com,
	LathaKannan Arumugam

[-- Attachment #1.1: Type: text/plain, Size: 4851 bytes --]

Thanks, Maciej! We’ll investigate!

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com>
Sent: Tuesday, June 29, 2021 9:39:59 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com>; Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Additionally, for claim that IPv4 does not do that, please provide Wireshark trace, if available.

On 29-Jun-21 18:36, Maciej Rabeda wrote:
Hi guys,

Finally got some time to look into it.

Long story short, this smells like infrastructure problem.
SARR passes over 546/547 port pair. That is between UEFI PXE client and DHCP server (even if it is the same machine).
The next packet is essentially a Boot Server choice step. UEFI PXE client sends a unicast discovery packet towards Boot server (same machine, same address) coded as DHCP Request.
The release packet is a direct reaction to 3 second timeout (see time diff between packet 9 and 11).

See section 2.2.1 in PXE spec: http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C6ba252758f3d4ef4eb2208d93b1c8cf8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605816087554815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Lb7ELKglF3Y%2Fdeg5aNdrt8WTPSpytI2kF%2FGm6CNTolQ%3D&reserved=0>

Please verify that your WDS service is running correctly, since clearly there is no reaction to that packet from Boot server.

[cid:part2.DA8CACBA.5A309C91@linux.intel.com]

On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
Can you please help us on this issues?
Get Outlook for Android<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C6ba252758f3d4ef4eb2208d93b1c8cf8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605816087564776%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7z98WyQ%2BYboLv47ti6v2Fe2iZbOWzuCJAVo0uYD4R7Q%3D&reserved=0>
________________________________
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io> on behalf of LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io><mailto:larumugam=microsoft.com@groups.io>
Sent: Friday, June 25, 2021 1:11:42 PM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Any inputs?

We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.

From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret

________________________________

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:

Just poking this to see if anyone has any ideas. Thanks!

[-- Attachment #1.2: Type: text/html, Size: 9394 bytes --]

[-- Attachment #2: knjfchcdfhflfima.png --]
[-- Type: image/png, Size: 69408 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-29 16:53                 ` Bret Barkelew
@ 2021-06-29 17:33                   ` Vincent Zimmer
  2021-06-29 18:54                     ` LathaKannan Arumugam
  0 siblings, 1 reply; 13+ messages in thread
From: Vincent Zimmer @ 2021-06-29 17:33 UTC (permalink / raw)
  To: devel@edk2.groups.io, bret.barkelew@microsoft.com,
	maciej.rabeda@linux.intel.com, LathaKannan Arumugam

[-- Attachment #1.1: Type: text/plain, Size: 6265 bytes --]

FYI
For IPv6, the TFTP-based network boot process (i.e., pxe) is called Netboot6 & detailed in "24.3.1 Netboot6"/" 24.3.1.2 IPv6-based PXE boot", and for IPV4 PXE we also curate changes/clarifications in "E.4.20 PXE 2.1 specification wire protocol clarifications", all of which are found in https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_03_18.pdf since http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C6ba252758f3d4ef4eb2208d93b1c8cf8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605816087554815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Lb7ELKglF3Y%2Fdeg5aNdrt8WTPSpytI2kF%2FGm6CNTolQ%3D&reserved=0> is frozen/unmaintained at this point.

Vincent

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Bret Barkelew via groups.io
Sent: Tuesday, June 29, 2021 9:54 AM
To: devel@edk2.groups.io; maciej.rabeda@linux.intel.com; LathaKannan Arumugam <larumugam@microsoft.com>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Thanks, Maciej! We'll investigate!

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Tuesday, June 29, 2021 9:39:59 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Additionally, for claim that IPv4 does not do that, please provide Wireshark trace, if available.
On 29-Jun-21 18:36, Maciej Rabeda wrote:
Hi guys,

Finally got some time to look into it.

Long story short, this smells like infrastructure problem.
SARR passes over 546/547 port pair. That is between UEFI PXE client and DHCP server (even if it is the same machine).
The next packet is essentially a Boot Server choice step. UEFI PXE client sends a unicast discovery packet towards Boot server (same machine, same address) coded as DHCP Request.
The release packet is a direct reaction to 3 second timeout (see time diff between packet 9 and 11).

See section 2.2.1 in PXE spec: http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C6ba252758f3d4ef4eb2208d93b1c8cf8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605816087554815%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Lb7ELKglF3Y%2Fdeg5aNdrt8WTPSpytI2kF%2FGm6CNTolQ%3D&reserved=0>

Please verify that your WDS service is running correctly, since clearly there is no reaction to that packet from Boot server.

[cid:image001.png@01D76CD2.39FA0EA0]
On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
Can you please help us on this issues?
Get Outlook for Android<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C6ba252758f3d4ef4eb2208d93b1c8cf8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605816087564776%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7z98WyQ%2BYboLv47ti6v2Fe2iZbOWzuCJAVo0uYD4R7Q%3D&reserved=0>
________________________________
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io> on behalf of LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io><mailto:larumugam=microsoft.com@groups.io>
Sent: Friday, June 25, 2021 1:11:42 PM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Any inputs?

We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.

From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret

________________________________

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:

Just poking this to see if anyone has any ideas. Thanks!

[-- Attachment #1.2: Type: text/html, Size: 12793 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 69408 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-29 17:33                   ` Vincent Zimmer
@ 2021-06-29 18:54                     ` LathaKannan Arumugam
  2021-06-30 21:44                       ` Bret Barkelew
  0 siblings, 1 reply; 13+ messages in thread
From: LathaKannan Arumugam @ 2021-06-29 18:54 UTC (permalink / raw)
  To: Zimmer, Vincent, devel@edk2.groups.io, Bret Barkelew,
	maciej.rabeda@linux.intel.com

[-- Attachment #1.1.1: Type: text/plain, Size: 9127 bytes --]

Thanks Vincent and Maciej for the your inputs. We made some more analysis and want your inputs for the same.

Test:1

  1.  DHCPv6 server replied with IANA,  Option 16(Vendor class with String as PxeClient), Option 59(Boot File URL with TFTP address), and Option 60 (BootFileParam)

Analysis: It is observed UEFI is trying to send boot server request based on the address mentioned in the boot file URL which is unicast. And this is done as part of SARR and as station IP is not assigned, the route lookup failed and packet dropped. If I use any link-local address in boot file URL , then request goes out. But in our case, PXE client and server are not on same link. So should the order be changed here. Finish SARR, assign Station IP and then do Boot server request.

Test:2
DHCPv6 server replied with IANA , Option 59(Boot File URL with TFTP address), and Option 60 (BootFileParam). I did not include Option 16(Pxe vendor string)
Analysis: It is observed that UEFI expects boot file length in 512 byte resolution and the did parsing was not in line with rfc5970 (ietf.org)<https://datatracker.ietf.org/doc/html/rfc5970#section-3.2>.  Can you tell us what is the expectation here? Please find the attached file for how option 60 is added by server.

Test:3

DHCPv6 server replied with IANA , Option 59(Boot File URL with TFTP address). I did not include Option 16(Pxe vendor string) and Option 60(BootFileParam)
As the reply does not carry PxeVendor string and boot file param, It is observed that UEFI finished SARR and station IPv6 was configured. It also went ahead and downloaded bootx64.efi file which was mentioned in option 59.
We also observed that UEFI loaded bootMgr and but eventually failed  with following error on screen.  We want UEFI to boot it in this method. Can you share us what needs to be done to move forward in this direction?

[cid:image002.png@01D76CDD.7C6F7350]

From: Zimmer, Vincent <vincent.zimmer@intel.com>
Sent: Tuesday, June 29, 2021 10:34 AM
To: devel@edk2.groups.io; Bret Barkelew <Bret.Barkelew@microsoft.com>; maciej.rabeda@linux.intel.com; LathaKannan Arumugam <larumugam@microsoft.com>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

FYI
For IPv6, the TFTP-based network boot process (i.e., pxe) is called Netboot6 & detailed in "24.3.1 Netboot6"/" 24.3.1.2 IPv6-based PXE boot", and for IPV4 PXE we also curate changes/clarifications in "E.4.20 PXE 2.1 specification wire protocol clarifications", all of which are found in https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_03_18.pdf<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuefi.org%2Fsites%2Fdefault%2Ffiles%2Fresources%2FUEFI_Spec_2_9_2021_03_18.pdf&data=04%7C01%7Clarumugam%40microsoft.com%7Cafc183026ca24e27207008d93b240d23%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605848791277983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Wj2an%2BxAYU%2B5BUOdSCmkCEFHW4Iv8NKFJu8UQt5nPm8%3D&reserved=0> since http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7Clarumugam%40microsoft.com%7Cafc183026ca24e27207008d93b240d23%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605848791277983%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FNW%2BpWWItrSh9XTiXsGxT8ILwB4zqoMXDX%2BCVyKt3RY%3D&reserved=0> is frozen/unmaintained at this point.

Vincent

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Bret Barkelew via groups.io
Sent: Tuesday, June 29, 2021 9:54 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Thanks, Maciej! We'll investigate!

- Bret
________________________________
From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Tuesday, June 29, 2021 9:39:59 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Additionally, for claim that IPv4 does not do that, please provide Wireshark trace, if available.
On 29-Jun-21 18:36, Maciej Rabeda wrote:
Hi guys,

Finally got some time to look into it.

Long story short, this smells like infrastructure problem.
SARR passes over 546/547 port pair. That is between UEFI PXE client and DHCP server (even if it is the same machine).
The next packet is essentially a Boot Server choice step. UEFI PXE client sends a unicast discovery packet towards Boot server (same machine, same address) coded as DHCP Request.
The release packet is a direct reaction to 3 second timeout (see time diff between packet 9 and 11).

See section 2.2.1 in PXE spec: http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7Clarumugam%40microsoft.com%7Cafc183026ca24e27207008d93b240d23%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605848791287976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TioS0NcUx6AEoPVkXpH95RcgAm1ngGSmBLVTVJNgirI%3D&reserved=0>

Please verify that your WDS service is running correctly, since clearly there is no reaction to that packet from Boot server.

[cid:image001.png@01D76CDA.A49138D0]
On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
Can you please help us on this issues?
Get Outlook for Android<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7Clarumugam%40microsoft.com%7Cafc183026ca24e27207008d93b240d23%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605848791297972%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5gwAGhFft7cbu7EMF09KdDgpxbj2uL9N0TIR%2B42%2BOA8%3D&reserved=0>
________________________________
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io> on behalf of LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io><mailto:larumugam=microsoft.com@groups.io>
Sent: Friday, June 25, 2021 1:11:42 PM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Any inputs?

We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.

From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret

________________________________

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:

Just poking this to see if anyone has any ideas. Thanks!

[-- Attachment #1.1.2: Type: text/html, Size: 19000 bytes --]

[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 69408 bytes --]

[-- Attachment #1.3: image002.png --]
[-- Type: image/png, Size: 231335 bytes --]

[-- Attachment #2: DHCPv6_Server.cap --]
[-- Type: image/cap, Size: 3508 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6
  2021-06-29 18:54                     ` LathaKannan Arumugam
@ 2021-06-30 21:44                       ` Bret Barkelew
  0 siblings, 0 replies; 13+ messages in thread
From: Bret Barkelew @ 2021-06-30 21:44 UTC (permalink / raw)
  To: LathaKannan Arumugam, Zimmer, Vincent, devel@edk2.groups.io,
	maciej.rabeda@linux.intel.com

[-- Attachment #1.1: Type: text/plain, Size: 10342 bytes --]

Maciej and Vincent,

We’ve captured data that demonstrates that EDK2 is handling IPv4 differently than IPv6. I’ve opened a bug to track this work:
3471 – Unexpected DHCP RELEASE after PXE server reply on IPv6; IPv4 handled differently (tianocore.org)<https://bugzilla.tianocore.org/show_bug.cgi?id=3471>

The captures were large, so I’ve shared them with OneDrive links.
The IPv4 capture shows that the UEFI is _not_ responding with a special UDP request.

Thoughts?

- Bret

From: LathaKannan Arumugam<mailto:larumugam@microsoft.com>
Sent: Tuesday, June 29, 2021 11:54 AM
To: Zimmer, Vincent<mailto:vincent.zimmer@intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>; maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Thanks Vincent and Maciej for the your inputs. We made some more analysis and want your inputs for the same.

Test:1

  1.  DHCPv6 server replied with IANA,  Option 16(Vendor class with String as PxeClient), Option 59(Boot File URL with TFTP address), and Option 60 (BootFileParam)

Analysis: It is observed UEFI is trying to send boot server request based on the address mentioned in the boot file URL which is unicast. And this is done as part of SARR and as station IP is not assigned, the route lookup failed and packet dropped. If I use any link-local address in boot file URL , then request goes out. But in our case, PXE client and server are not on same link. So should the order be changed here. Finish SARR, assign Station IP and then do Boot server request.

Test:2
DHCPv6 server replied with IANA , Option 59(Boot File URL with TFTP address), and Option 60 (BootFileParam). I did not include Option 16(Pxe vendor string)
Analysis: It is observed that UEFI expects boot file length in 512 byte resolution and the did parsing was not in line with rfc5970 (ietf.org)<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc5970%23section-3.2&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C2810d8102cea4be5741208d93b2f4e7e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605896636463718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=z6b5uIqrd7xDaa6EtAoiggvG1UgufNQrOuRBH4oK0gY%3D&reserved=0>.  Can you tell us what is the expectation here? Please find the attached file for how option 60 is added by server.

Test:3

DHCPv6 server replied with IANA , Option 59(Boot File URL with TFTP address). I did not include Option 16(Pxe vendor string) and Option 60(BootFileParam)
As the reply does not carry PxeVendor string and boot file param, It is observed that UEFI finished SARR and station IPv6 was configured. It also went ahead and downloaded bootx64.efi file which was mentioned in option 59.
We also observed that UEFI loaded bootMgr and but eventually failed  with following error on screen.  We want UEFI to boot it in this method. Can you share us what needs to be done to move forward in this direction?

[cid:image003.png@01D76DBE.63C70480]

From: Zimmer, Vincent <vincent.zimmer@intel.com>
Sent: Tuesday, June 29, 2021 10:34 AM
To: devel@edk2.groups.io; Bret Barkelew <Bret.Barkelew@microsoft.com>; maciej.rabeda@linux.intel.com; LathaKannan Arumugam <larumugam@microsoft.com>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

FYI
For IPv6, the TFTP-based network boot process (i.e., pxe) is called Netboot6 & detailed in “24.3.1 Netboot6”/” 24.3.1.2 IPv6-based PXE boot", and for IPV4 PXE we also curate changes/clarifications in “E.4.20 PXE 2.1 specification wire protocol clarifications”, all of which are found in https://uefi.org/sites/default/files/resources/UEFI_Spec_2_9_2021_03_18.pdf<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuefi.org%2Fsites%2Fdefault%2Ffiles%2Fresources%2FUEFI_Spec_2_9_2021_03_18.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C2810d8102cea4be5741208d93b2f4e7e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605896636473672%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iVMicYpEcGSV1wNXEL9zDV2%2F5ZeK5jFgFabbCwuk%2FUU%3D&reserved=0> since http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C2810d8102cea4be5741208d93b2f4e7e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605896636473672%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2FXkhfh7PmOXMn4Tu2uG6Dk2GMYaaFwlhlhnSB8oYonA%3D&reserved=0> is frozen/unmaintained at this point.

Vincent

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Bret Barkelew via groups.io
Sent: Tuesday, June 29, 2021 9:54 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Thanks, Maciej! We’ll investigate!

- Bret

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Tuesday, June 29, 2021 9:39:59 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Additionally, for claim that IPv4 does not do that, please provide Wireshark trace, if available.
On 29-Jun-21 18:36, Maciej Rabeda wrote:
Hi guys,

Finally got some time to look into it.

Long story short, this smells like infrastructure problem.
SARR passes over 546/547 port pair. That is between UEFI PXE client and DHCP server (even if it is the same machine).
The next packet is essentially a Boot Server choice step. UEFI PXE client sends a unicast discovery packet towards Boot server (same machine, same address) coded as DHCP Request.
The release packet is a direct reaction to 3 second timeout (see time diff between packet 9 and 11).

See section 2.2.1 in PXE spec: http://www.pix.net/software/pxeboot/archive/pxespec.pdf<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pix.net%2Fsoftware%2Fpxeboot%2Farchive%2Fpxespec.pdf&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C2810d8102cea4be5741208d93b2f4e7e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605896636483629%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9mwsE3chGgjMSgKQE0dklTdNuhZvdmNdIyxzi%2F7wZ%2Fs%3D&reserved=0>

Please verify that your WDS service is running correctly, since clearly there is no reaction to that packet from Boot server.

[cid:image001.png@01D76CDA.A49138D0]
On 28-Jun-21 22:05, LathaKannan Arumugam via groups.io wrote:
Can you please help us on this issues?
Get Outlook for Android<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg&data=04%7C01%7CBret.Barkelew%40microsoft.com%7C2810d8102cea4be5741208d93b2f4e7e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637605896636483629%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=sy2x%2FAcNazfbhrDsCVX4780KkKf8qdjNG6yKD7W2BxM%3D&reserved=0>

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io> on behalf of LathaKannan Arumugam via groups.io <larumugam=microsoft.com@groups.io><mailto:larumugam=microsoft.com@groups.io>
Sent: Friday, June 25, 2021 1:11:42 PM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io><mailto:devel@edk2.groups.io>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Any inputs?

We kind of blocked on this for a week.  Kindly look into packet capture and suggest a path forward.

From: LathaKannan Arumugam
Sent: Friday, June 25, 2021 9:23 AM
To: Bret Barkelew <Bret.Barkelew@microsoft.com><mailto:Bret.Barkelew@microsoft.com>; Rabeda, Maciej <maciej.rabeda@linux.intel.com><mailto:maciej.rabeda@linux.intel.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Attached packet captured from server.

From: Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Sent: Friday, June 25, 2021 9:19 AM
To: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; LathaKannan Arumugam <larumugam@microsoft.com<mailto:larumugam@microsoft.com>>
Subject: Re: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

+ @LathaKannan Arumugam<mailto:larumugam@microsoft.com>

- Bret

From: Rabeda, Maciej <maciej.rabeda@linux.intel.com<mailto:maciej.rabeda@linux.intel.com>>
Sent: Friday, June 25, 2021 7:40:16 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>; Bret Barkelew <Bret.Barkelew@microsoft.com<mailto:Bret.Barkelew@microsoft.com>>
Subject: [EXTERNAL] Re: [edk2-devel] NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6

Looking at it. Any chance to get Wireshark trace for this scenario?

On 25-Jun-21 09:25, brbarkel via groups.io wrote:

Just poking this to see if anyone has any ideas. Thanks!

[-- Attachment #1.2: Type: text/html, Size: 21019 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 69408 bytes --]

[-- Attachment #3: D69B36B6AC6841BB8FDB55D570561B53.png --]
[-- Type: image/png, Size: 286320 bytes --]

[-- Attachment #4: 2DE378E8AEA048A2B6C74BF16B651720.png --]
[-- Type: image/png, Size: 141 bytes --]

[-- Attachment #5: DA1BAD5431864482A26DD838DE240250.png --]
[-- Type: image/png, Size: 137 bytes --]

[-- Attachment #6: 453836353A2041E6BAF497633F089500.png --]
[-- Type: image/png, Size: 140 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2021-06-30 21:44 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-06-23 21:08 NetworkPkg: Unexpected DHCP RELEASE after PXE server reply on IPv6 Bret Barkelew
2021-06-25  7:25 ` [edk2-devel] " brbarkel
2021-06-25 14:40   ` Maciej Rabeda
2021-06-25 16:19     ` [EXTERNAL] " Bret Barkelew
2021-06-25 16:22       ` larumugam
2021-06-25 20:11         ` LathaKannan Arumugam
     [not found]         ` <168BEC4CE79D1C8A.1293@groups.io>
2021-06-28 20:05           ` LathaKannan Arumugam
2021-06-29 16:36             ` Maciej Rabeda
     [not found]             ` <168D1AEBDC669830.32494@groups.io>
2021-06-29 16:39               ` Maciej Rabeda
2021-06-29 16:53                 ` Bret Barkelew
2021-06-29 17:33                   ` Vincent Zimmer
2021-06-29 18:54                     ` LathaKannan Arumugam
2021-06-30 21:44                       ` Bret Barkelew

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox