From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 154352095C3A6 for ; Tue, 11 Apr 2017 02:28:52 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6F80282047 for ; Tue, 11 Apr 2017 15:00:31 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6348882046 for ; Tue, 11 Apr 2017 15:00:30 +0530 (IST) Received: from webmail.amiindia.co.in (venus1.in.megatrends.com [10.0.0.5]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS for ; Tue, 11 Apr 2017 15:00:30 +0530 (IST) Received: from VENUS2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b]) by VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5%14]) with mapi id 14.01.0438.000; Tue, 11 Apr 2017 14:58:47 +0530 From: Santhapur Naveen To: "edk2-devel@lists.01.org" Thread-Topic: What happens if I have 2 DNS in the OFFER packet Thread-Index: AdKypFDRlov2r+EIQK+Qt2aVrl0+lA== Date: Tue, 11 Apr 2017 09:28:47 +0000 Message-ID: <625A2455CC232F40B0F38F05ACED6D97C86789BF@Venus2.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.77] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-22998.006 X-TM-AS-Result: No--14.945-5.0-31-10 X-imss-scan-details: No--14.945-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-22998.006 X-TMASE-Result: 10--14.944600-10.000000 X-TMASE-MatchedRID: Us0/2dvwd0SA/l0nirxEGIzb2GR6Ttd3s1hEwUD1d/I3Z3efQH+wj38k Ftize7mxLNAU+azLX58s4TYPtim38z/UFFoyjv+4RVrD26noGI4pWss5kPUFdDvpyveVkrtEibB 1dtAWP9iL5e1LZJn6mI5FOnAjuzgNKpm0ussYianvVbHa5Rs8t0OvwxWboMrdMDg31Je5iSmM0v GtzEpWJYyRWx0wlnUGf6WytOayZdvWV8MKb34RlVgowyUWHgGdh+w9Wz/xXDoR8rMICe0qkPMxs +ucp3ZM7gzcfk5O5gtiXQjTxUn166dwsJe6fN2LEgwM8US/pTFE2/eTT+Z+iCSuWQWhw7iTuF0B EedRtW2kSBTXCEpAxeG1Uq6sRNO/KGxJMBjfwlV/HPKCjG4GGH17zx+CiSWzDC/Vm90If4WY8y8 WI7jQsI8vWR6sDTLkNnT+Saflf/GXBXaJoB9JZxRFJJyf5BJe2K+lN2ZUJHbZs3HUcS/scFRbT8 n8vMswuJyX3hv9IOBOGo0kG9NhOiKFafra71Y5CvW26gT+vlZlSN5cV310prwxdV5t0a/+O8HsM JTouZmiqFg0yHOwmUshdtDOe1RdNmSl9BlR2Hg= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: What happens if I have 2 DNS in the OFFER packet X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Apr 2017 09:28:52 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, I've been facing an issue which is "IP is not assigned to the S= UT if the received OFFER packet contains 2 DNS entries." I don't have the environment with me. When I compared the Wires= hark log in success and failure cases sent to me, I see no differences exce= pt 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 b= e 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