From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"maciej.rabeda@linux.intel.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
Date: Tue, 29 Jun 2021 16:53:58 +0000 [thread overview]
Message-ID: <MW4PR21MB1907D167F3DB69BC5C94CFAEEF029@MW4PR21MB1907.namprd21.prod.outlook.com> (raw)
In-Reply-To: <9384fd3c-2ceb-cbb7-e7f7-c2ddfa8eb3ec@linux.intel.com>
[-- 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 --]
next prev parent reply other threads:[~2021-06-29 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-06-29 17:33 ` Vincent Zimmer
2021-06-29 18:54 ` LathaKannan Arumugam
2021-06-30 21:44 ` Bret Barkelew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MW4PR21MB1907D167F3DB69BC5C94CFAEEF029@MW4PR21MB1907.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox