From owner-freebsd-current@freebsd.org Wed Jul 22 13:04: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 74E979A664F; Wed, 22 Jul 2015 13:04:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 182C41231; Wed, 22 Jul 2015 13:04:26 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wibud3 with SMTP id ud3so171489634wib.0; Wed, 22 Jul 2015 06:04:24 -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:content-transfer-encoding; bh=XUWtIvknuaYbJ/zGMP25mxh33UsA33u14tWOOTEQAAc=; b=YFiwaRErZDc5DVxDcDjelEp5CMk/3ZW6z42273/WOITjJR7QTPetueHD6+6wM6qE1P 0wYh/21Qh+RhPtl9z4weXys4j0lyjldkrfpheCcBsCnbDjCiokY5xYJPHMapTm3lp2Q8 VUA6xOOWw8uVWvWULMo49YwZCrhulwg4R6sy8i3RcJ2tOj/2vLLQQdKKw0xbvnYUNkR+ 2SuCLjoPTnKXW6jRK3M/A8wPLjVBsXu0a212vqmk/BmqxvKmRivwsxe82MVEF4dbZNwi 5XRRKujd/CiphToEq8nboM2yHqsq7r0l94aa4TVNklvJFWNQjWO2utwTA/FnHmjN1TO5 GdsQ== MIME-Version: 1.0 X-Received: by 10.180.198.178 with SMTP id jd18mr41761623wic.14.1437570264436; Wed, 22 Jul 2015 06:04:24 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Wed, 22 Jul 2015 06:04:24 -0700 (PDT) In-Reply-To: References: <20150707130902.GA41189@zxy.spb.ru> <20150707154906.GA44094@zxy.spb.ru> Date: Wed, 22 Jul 2015 16:04:24 +0300 Message-ID: Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V From: Pavel Timofeev To: Wei Hu Cc: Slawa Olhovchenkov , "freebsd-current@freebsd.org" , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Wed, 22 Jul 2015 13:04:26 -0000 Hi! I see you have done the code for disabling UDP checksum offloading when running on the Hyper-V on Windows Server 2012 and earlier hosts https://svnweb.freebsd.org/base?view=3Drevision&revision=3D285785 I tried new CURRENT and it works. Thank you! A small note here: while it disables and works it still shows RXCSUM and TSCSUM in iface's options: root@proxy:/usr/src # ifconfig hn0 hn0: flags=3D8843 metric 0 mtu 1500 options=3D31b ether 00:15:5d:02:9c:09 inet 192.168.25.26 netmask 0xffffffc0 broadcast 192.168.25.63 nd6 options=3D29 Is it possible to hide it automatically if it's disabled by new code? 2015-07-13 11:06 GMT+03:00 Wei Hu : > We have root caused the problem. This issue happens on the Hyper-Vs on Wi= ndows Server 2012 (Win 8.0) and earlier releases. On these releases, the UP= D checksum offloading on host side does not work properly. The workaround i= s to disable UPD checksum offloading in the FreeBSD guest through 'ifconfig= '. We are also working on a patch to turn off UPD checksum offloading in th= e netvsc driver when detecting the Hyper-V releases. > > The UDP checksum offloading works fine on Windows Server 2012R2 and Win 8= .1 hosts. > > Thanks Pavel and Slawa for the support. > > Wei > > >> -----Original Message----- >> From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd- >> virtualization@freebsd.org] On Behalf Of Pavel Timofeev >> Sent: Wednesday, July 8, 2015 4:06 PM >> To: Slawa Olhovchenkov >> Cc: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org >> Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V >> >> Ok, r284746 is the root of the problem. MS DNS works under r284745 and >> doesn't work under r284746. >> Slawa, what should I look at in wireshark output? >> >> >> 2015-07-07 18:49 GMT+03:00 Slawa Olhovchenkov : >> > On Tue, Jul 07, 2015 at 06:04:46PM +0300, Pavel Timofeev wrote: >> > >> >> Well, turning off checksum offloading by `ifconfig hn0 -txcsum >> >> -rxcsum` definitely helps. >> >> >> >> As for tcpdump I'm not completely sure if I did it right, but I see >> >> "bad udp cksum" phrase: >> >> >> >> # tcpdump -i hn0 -vvv -nn udp dst port 53 >> >> tcpdump: listening on hn0, link-type EN10MB (Ethernet), capture size >> >> 262144 bytes >> >> 18:01:19.139994 IP (tos 0x0, ttl 64, id 61218, offset 0, flags >> >> [none], proto UDP (17), length 51) >> >> 192.168.25.26.45683 > 192.168.25.3.53: [bad udp cksum 0xb39e -> >> >> 0xf210!] 52886+ A? ya.ru. (23) >> >> 18:01:24.140544 IP (tos 0x0, ttl 64, id 17293, offset 0, flags >> >> [none], proto UDP (17), length 51) >> >> 192.168.25.26.12575 > 192.168.25.3.53: [bad udp cksum 0xb39e -> >> >> 0x7365!] 52886+ A? ya.ru. (23) >> > >> > tcpdump "bad udp cksum" is normal on FreeBSD host in case checksum >> > offload (and may be need only for help finding issuse in code). Need >> > wireshark capturing from MS DNS host (or from mirroring port). >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization- >> unsubscribe@freebsd.org"