From owner-freebsd-current@freebsd.org Tue Jul 7 13:55:41 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A45BB995812; Tue, 7 Jul 2015 13:55:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3818811F6; Tue, 7 Jul 2015 13:55:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wiwl6 with SMTP id l6so315518430wiw.0; Tue, 07 Jul 2015 06:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WJIHvJPa0Og9qb8qR2Ppvg5lZkeWy3bCbj2za2QEPjw=; b=yjGw4NwCnd2uYNDoG0a0BueDEiNcu1u4uU5A4vTGQenJLjOk4y5v6v6RjCNiGiR8JQ aad/kStqyxFaTQwN3EVK/vkD2agaO/VTbBu8VPjAF9Ilb1/VvIFKvRMNy76EEWCIZ+h4 WJW6Q4O2Utw7ZL/XHPrO5guRxSQbkVl9HyU4yTE832KFPySazWUTjRmWbA3uqrGEKEXi 1lYx2aDKIL4AzazyV/dPrLHVCXt15nApDnXRii+cemN5curh2XK15v9h7P+FuDUeMSWb G7y9tODwj+I0we/eIQlMYhSJC3C9l+IBe+U6viF4LFqlasW5akOCFeSuYXyWPw3uNDZq pJYA== MIME-Version: 1.0 X-Received: by 10.180.37.230 with SMTP id b6mr63984260wik.14.1436277339417; Tue, 07 Jul 2015 06:55:39 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 06:55:39 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jul 2015 16:55:39 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Wei Hu Cc: "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Tue, 07 Jul 2015 14:01:46 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2015 13:55:41 -0000 Wow, r284746 was MFCed to 10 STABLE! I should hurry up! 2015-07-07 16:26 GMT+03:00 Pavel Timofeev : > Ok, I'll try r284745 and then r284746 and see what happens. > > 2015-07-07 16:06 GMT+03:00 Wei Hu : >>> -----Original Message----- >>> From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd- >>> virtualization@freebsd.org] On Behalf Of Pavel Timofeev >>> Sent: Tuesday, July 7, 2015 7:51 PM >>> To: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org >>> Subject: MS DNS doesn't answer to CURRENT under Hyper-V >>> >>> Hi! >>> I have a test virtual machine which runs CURRENT under Hyper-V. It's >>> amd64 r285198 now. >>> It can't get any response from MS DNS server. Well, it could two or three >>> weeks ago, but after upgrade it's not able to do it anymore. >>> Google DNS answers without problems meanwhile (sic!). >>> >>> What I do: >>> # host google.ru 192.168.25.3 >>> I see that MS DNS (192.168.25.3) server receives these packets, but ignores >>> them. >>> And no matter how my system asks MS DNS. Every daemon can't get >>> response too. >>> >>> I know that nothing was changed in MS DNS server. No doubt. >>> Then I tried different available CURRENT snapshot ISOs. >>> >>> FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso - MS DNS does >>> not answer. >>> >>> FreeBSD-11.0-CURRENT-amd64-20150625-r284814-disc1.iso - MS DNS does >>> not answer. >>> >>> FreeBSD-11.0-CURRENT-amd64-20150618-r284544-disc1.iso - MS DNS >>> answers! >>> >>> So something was committed to CURRENT between 20150618 and 20150625. >>> This something ruins communication with MS DNS. >>> >> There was a commit for Hyper-V TSO and checksum offloading support (r284746) on >> June 24th. I think this commit is the cause. Can you verify the MS DNS behavior between >> The builds of June 23rd and 24th? I will take a look of this issue tomorrow. >> >> Thanks, >> Wei >> >> >>