RE: MS DNS doesn't answer to CURRENT under Hyper-V
Just committed the fix in releng/10.2 branch as r286058. Wei > -Original Message- > From: Pavel Timofeev [mailto:tim...@gmail.com] > Sent: Wednesday, July 29, 2015 3:48 PM > To: Wei Hu > Cc: Slawa Olhovchenkov ; freebsd-current@freebsd.org; > freebsd-virtualizat...@freebsd.org > Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V > > Hi! > r285785 still isn't MFCed. > RC2 is coming soon. > > 2015-07-23 10:54 GMT+03:00 Pavel Timofeev : > > Ok, sorry! > > > > 2015-07-23 7:51 GMT+03:00 Wei Hu : > >> The TCP offloading is still working on these platforms. There is no flag to > distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set. > Let me know if there is any other way to show it properly. > >> > >> Thanks, > >> Wei > >> > >> > >> -----Original Message- > >> From: Pavel Timofeev [mailto:tim...@gmail.com] > >> Sent: Wednesday, July 22, 2015 9:04 PM > >> To: Wei Hu > >> Cc: Slawa Olhovchenkov ; freebsd- > curr...@freebsd.org; > >> freebsd-virtualizat...@freebsd.org > >> Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V > >> > >> 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=revision&revision=285785 > >> > >> 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=8843 metric > 0 mtu 1500 > >> > options=31b > >> ether 00:15:5d:02:9c:09 > >> inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63 > >> nd6 options=29 > >> > >> 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 Windows Server 2012 (Win 8.0) and earlier releases. On these releases, > the UPD checksum offloading on host side does not work properly. The > workaround is 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 the 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-virtualizat...@freebsd.org > >>>> [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of > >>>> Pavel Timofeev > >>>> Sent: Wednesday, July 8, 2015 4:06 PM > >>>> To: Slawa Olhovchenkov > >>>> Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@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-virtualizat...@freebsd.org mailing list > >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > >>>> To unsubscribe, send any mail to "freebsd-virtualization- > >>>> unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: MS DNS doesn't answer to CURRENT under Hyper-V
It is already in stable/10 branch. I am just about to send the request to re@ for releng/10.2 commit approval. Wei -Original Message- From: Pavel Timofeev [mailto:tim...@gmail.com] Sent: Wednesday, July 29, 2015 3:48 PM To: Wei Hu Cc: Slawa Olhovchenkov ; freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V Hi! r285785 still isn't MFCed. RC2 is coming soon. 2015-07-23 10:54 GMT+03:00 Pavel Timofeev : > Ok, sorry! > > 2015-07-23 7:51 GMT+03:00 Wei Hu : >> The TCP offloading is still working on these platforms. There is no flag to >> distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set. >> Let me know if there is any other way to show it properly. >> >> Thanks, >> Wei >> >> >> -Original Message- >> From: Pavel Timofeev [mailto:tim...@gmail.com] >> Sent: Wednesday, July 22, 2015 9:04 PM >> To: Wei Hu >> Cc: Slawa Olhovchenkov ; freebsd-current@freebsd.org; >> freebsd-virtualizat...@freebsd.org >> Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V >> >> 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=revision&revision=285785 >> >> 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=8843 metric 0 mtu 1500 >> options=31b >> ether 00:15:5d:02:9c:09 >> inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63 >> nd6 options=29 >> >> 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 >>> Windows Server 2012 (Win 8.0) and earlier releases. On these releases, the >>> UPD checksum offloading on host side does not work properly. The workaround >>> is 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 the 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-virtualizat...@freebsd.org >>>> [mailto:owner-freebsd- virtualizat...@freebsd.org] On Behalf Of >>>> Pavel Timofeev >>>> Sent: Wednesday, July 8, 2015 4:06 PM >>>> To: Slawa Olhovchenkov >>>> Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@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-virtualizat...@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >>>> To unsubscribe, send any mail to "freebsd-virtualization- >>>> unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: MS DNS doesn't answer to CURRENT under Hyper-V
The TCP offloading is still working on these platforms. There is no flag to distinguish UDP and TCP offloading, so the RXCSUM and TXCSUM are still set. Let me know if there is any other way to show it properly. Thanks, Wei -Original Message- From: Pavel Timofeev [mailto:tim...@gmail.com] Sent: Wednesday, July 22, 2015 9:04 PM To: Wei Hu Cc: Slawa Olhovchenkov ; freebsd-current@freebsd.org; freebsd-virtualizat...@freebsd.org Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V 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=revision&revision=285785 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=8843 metric 0 mtu 1500 options=31b ether 00:15:5d:02:9c:09 inet 192.168.25.26 netmask 0xffc0 broadcast 192.168.25.63 nd6 options=29 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 > Windows Server 2012 (Win 8.0) and earlier releases. On these releases, the > UPD checksum offloading on host side does not work properly. The workaround > is 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 the 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-virtualizat...@freebsd.org [mailto:owner-freebsd- >> virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev >> Sent: Wednesday, July 8, 2015 4:06 PM >> To: Slawa Olhovchenkov >> Cc: freebsd-current@freebsd.org; freebsd-virtualizat...@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-virtualizat...@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization- >> unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: MS DNS doesn't answer to CURRENT under Hyper-V
> -Original Message- > From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- > virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev > Sent: Tuesday, July 7, 2015 7:51 PM > To: freebsd-current@freebsd.org; freebsd-virtualizat...@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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
