zation@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 :
> >&
;
freebsd-virtualization@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
5 9:04 PM
>> To: Wei Hu
>> Cc: Slawa Olhovchenkov ; freebsd-curr...@freebsd.org;
>> freebsd-virtualization@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 whe
; 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-virtualization@freebsd.org
> Subject: Re: MS DNS doesn't
...@gmail.com]
Sent: Wednesday, July 22, 2015 9:04 PM
To: Wei Hu
Cc: Slawa Olhovchenkov ; freebsd-curr...@freebsd.org;
freebsd-virtualization@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 o
t;>
>> 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
>>>
Pavel Timofeev
>> Sent: Wednesday, July 8, 2015 4:06 PM
>> To: Slawa Olhovchenkov
>> Cc: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
>> Subject: Re: MS DNS doesn't answer to CURRENT under Hyper-V
>>
>> Ok, r284746 is the root o
ject: 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 Wed, Jul 08, 2015 at 11:05:39AM +0300, Pavel Timofeev wrote:
> 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?
I think developers can want look at same packet before entering in NIC
and aft
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 of
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 po
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
2621
; 2015-07-07 16:06 GMT+03:00 Wei Hu :
> >> >>> -Original Message-
> >> >>> From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd-
> >> >>> virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev
> >> >>> Se
gt; Sent: Tuesday, July 7, 2015 7:51 PM
>> >>> To: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
>> >>> Subject: MS DNS doesn't answer to CURRENT under Hyper-V
>> >>>
>> >>> Hi!
>> >>> I have a t
.org [mailto:owner-freebsd-
> >>> virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev
> >>> Sent: Tuesday, July 7, 2015 7:51 PM
> >>> To: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
> >>> Subject: MS DNS doesn't answer to CURRENT
zat...@freebsd.org [mailto:owner-freebsd-
>>> virtualizat...@freebsd.org] On Behalf Of Pavel Timofeev
>>> Sent: Tuesday, July 7, 2015 7:51 PM
>>> To: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
>>> Subject: MS DNS doesn't answer to CURRE
Tuesday, July 7, 2015 7:51 PM
>> To: freebsd-curr...@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 r
On Tue, Jul 07, 2015 at 02:50:49PM +0300, Pavel Timofeev wrote:
> 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 anymor
ct: 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
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
20 matches
Mail list logo