From: "Maciej Rabeda" <maciej.rabeda@linux.intel.com>
To: devel@edk2.groups.io, 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
Date: Tue, 29 Jun 2021 18:36:57 +0200 [thread overview]
Message-ID: <8a13d715-1f9d-4ca6-508f-4055832d7f20@linux.intel.com> (raw)
In-Reply-To: <BYAPR21MB1303F29570532FC7D1515AAFB8039@BYAPR21MB1303.namprd21.prod.outlook.com>
[-- 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 --]
next prev parent reply other threads:[~2021-06-29 16:37 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 [this message]
[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
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=8a13d715-1f9d-4ca6-508f-4055832d7f20@linux.intel.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