From: larumugam@microsoft.com
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
Date: Fri, 25 Jun 2021 16:22:55 +0000 [thread overview]
Message-ID: <BYAPR21MB13039230A324E891075BF8C6B8069@BYAPR21MB1303.namprd21.prod.outlook.com> (raw)
In-Reply-To: <MW4PR21MB19071831EC212DF998366306EF069@MW4PR21MB1907.namprd21.prod.outlook.com>
[-- 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 --]
next prev parent reply other threads:[~2021-06-25 16:22 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 [this message]
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
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=BYAPR21MB13039230A324E891075BF8C6B8069@BYAPR21MB1303.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