From: Santhapur Naveen <naveens@amiindia.co.in>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: What happens if I have 2 DNS in the OFFER packet
Date: Tue, 11 Apr 2017 09:28:47 +0000 [thread overview]
Message-ID: <625A2455CC232F40B0F38F05ACED6D97C86789BF@Venus2.in.megatrends.com> (raw)
Hi all,
I've been facing an issue which is "IP is not assigned to the SUT if the received OFFER packet contains 2 DNS entries."
I don't have the environment with me. When I compared the Wireshark log in success and failure cases sent to me, I see no differences except the DNS entries in the OFFFER are different.
In the failure case, DISCOVER packet is sent four times as per RFC. And the server is sending OFFER packet all the four times, but the SUT is not accepting. Since I don't have the environment in which there will be two DNS entries, I'm not in a position to provide more details.
Is this an expected behavior or am I missing anything?
Regards,
Naveen
next reply other threads:[~2017-04-11 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 9:28 Santhapur Naveen [this message]
2017-04-11 11:29 ` What happens if I have 2 DNS in the OFFER packet Wu, Jiaxin
2017-04-11 11:31 ` Santhapur Naveen
2017-04-11 11:35 ` Wu, Jiaxin
2017-04-11 11:36 ` Santhapur Naveen
2017-04-12 7:43 ` Wu, Jiaxin
[not found] ` <625A2455CC232F40B0F38F05ACED6D97C8678F71@Venus2.in.megatrends.com>
[not found] ` <895558F6EA4E3B41AC93A00D163B7274162C01C4@SHSMSX103.ccr.corp.intel.com>
[not found] ` <625A2455CC232F40B0F38F05ACED6D97C867B4EA@Venus2.in.megatrends.com>
2017-04-19 5:15 ` Wu, Jiaxin
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=625A2455CC232F40B0F38F05ACED6D97C86789BF@Venus2.in.megatrends.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