From owner-freebsd-current@freebsd.org Tue Jul 7 13:26:26 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 E3C5C9950E3; Tue, 7 Jul 2015 13:26:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (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 7DB111EDD; Tue, 7 Jul 2015 13:26:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wibdq8 with SMTP id dq8so183061553wib.1; Tue, 07 Jul 2015 06:26:25 -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=JKzn7Yg9H4+2S+207Tw+wAYPdU2CBMar/TgWew7Msqc=; b=ax5nGpUp4wvFKi4dRaevqBozhSgtKcQo3AZmnGiSJwShP1sARW5ymTSJOZAsny6kez L/BIpA7Tzj9INXg/UktxNTA3LLgeBT09UwvehobgEIpEK4ICFrtaWyrjeteYPl+ugK/r 0V8hHlbcn9ry8fSsRbZPjE7BOUGNbJhTfeOAa+bQrGnj/7KLFoo5hYFM5Iz5AsjxBwuu jdA++FP74r7HFzFA7xxM8hkRL62zg8chnc1cohMDR9Zp8Phh0KCKmH35XBa8hTvxQ8U8 p1VBJ2x1E3ZNGCv9APKHkqlDvcrE4xrpQM8UF4yOSFoj1ndoG7ZYBoDJW9EBnhCb/Nyt VWTA== MIME-Version: 1.0 X-Received: by 10.180.81.38 with SMTP id w6mr69242920wix.14.1436275585034; Tue, 07 Jul 2015 06:26:25 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Tue, 7 Jul 2015 06:26:24 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Jul 2015 16:26:24 +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 13:51:44 +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:26:27 -0000 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 > > >