public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Jiaxin" <jiaxin.wu@intel.com>
To: Santhapur Naveen <naveens@amiindia.co.in>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: What happens if I have 2 DNS in the OFFER packet
Date: Tue, 11 Apr 2017 11:35:30 +0000	[thread overview]
Message-ID: <895558F6EA4E3B41AC93A00D163B7274162BF687@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C8678A6C@Venus2.in.megatrends.com>

Ok, I will try it tomorrow morning, then update it to you. Thanks report.

Thanks,
Jiaxin  

> -----Original Message-----
> From: Santhapur Naveen [mailto:naveens@amiindia.co.in]
> Sent: Tuesday, April 11, 2017 7:32 PM
> To: Wu, Jiaxin <jiaxin.wu@intel.com>; edk2-devel@lists.01.org
> Subject: RE: What happens if I have 2 DNS in the OFFER packet
> 
> Hi Jiaxin,
> 
> 	Yeah, I've been using 'ifconfig -s eth0 dhcp' from shell to set the IP
> address.
> 
> Regards,
> Naveen
> 
> -----Original Message-----
> From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com]
> Sent: Tuesday, April 11, 2017 5:00 PM
> To: Santhapur Naveen; edk2-devel@lists.01.org
> Subject: RE: What happens if I have 2 DNS in the OFFER packet
> 
> Hi Naveen,
> 
> Do you use the "ifconfig -s eth0 dhcp" command to set the IP address? For
> Ip4config2 protocol, no matter how many DNS in offer packet, all of will be
> configured (See Ip4Config2OnDhcp4Complete).
> 
> Thanks,
> Jiaxin
> 
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > Santhapur Naveen
> > Sent: Tuesday, April 11, 2017 5:29 PM
> > To: edk2-devel@lists.01.org
> > Subject: [edk2] What happens if I have 2 DNS in the OFFER packet
> >
> > 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
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2017-04-11 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  9:28 What happens if I have 2 DNS in the OFFER packet Santhapur Naveen
2017-04-11 11:29 ` Wu, Jiaxin
2017-04-11 11:31   ` Santhapur Naveen
2017-04-11 11:35     ` Wu, Jiaxin [this message]
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=895558F6EA4E3B41AC93A00D163B7274162BF687@SHSMSX103.ccr.corp.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