From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: macvlan device blocks traffic for 30 secs Date: Thu, 25 Feb 2010 18:19:46 +0100 Message-ID: <4B86B132.9090906@trash.net> References: <4B86AB36.6090402@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Netfilter Developer Mailing List To: Jan Engelhardt Return-path: Received: from stinky.trash.net ([213.144.137.162]:37930 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932989Ab0BYRTr (ORCPT ); Thu, 25 Feb 2010 12:19:47 -0500 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Jan Engelhardt wrote: > On Thursday 2010-02-25 17:54, Patrick McHardy wrote: >> Jan Engelhardt wrote: >>> it's a while since I have last toyed with macvlan, but for some >>> experimenting, it came up as something usable again. What I noticed >>> while testing: >>> >>> guest# ip link add link eth0 name mqv0 type macvlan >>> guest# ip link set dev mqv0 up >>> >>> At this point, any connections drop for a specific amount of time. >>> >>> host$ ping 192.168.100.101 >>> PING 192.168.100.101 (192.168.100.101) 56(84) bytes of data. >>> 64 bytes from 192.168.100.101: icmp_seq=1 ttl=64 time=4.87 ms >>> 64 bytes from 192.168.100.101: icmp_seq=2 ttl=64 time=0.353 ms >>> 64 bytes from 192.168.100.101: icmp_seq=3 ttl=64 time=0.341 ms >>> 64 bytes from 192.168.100.101: icmp_seq=4 ttl=64 time=0.335 ms >>> 64 bytes from 192.168.100.101: icmp_seq=5 ttl=64 time=0.345 ms >>> 64 bytes from 192.168.100.101: icmp_seq=6 ttl=64 time=0.378 ms >>> 64 bytes from 192.168.100.101: icmp_seq=7 ttl=64 time=0.283 ms >>> 64 bytes from 192.168.100.101: icmp_seq=8 ttl=64 time=0.372 ms >>> 64 bytes from 192.168.100.101: icmp_seq=37 ttl=64 time=5.04 ms >>> 64 bytes from 192.168.100.101: icmp_seq=38 ttl=64 time=0.291 ms >>> >>> and I am not quite sure why that is. The ARP entries don't change. >>> Can you reproduce this? >> No, this works fine here. It might be related to filter reprogramming >> of the NIC. Which driver are you using? > > tap0 on one the host, e1000 inside the virtualbox. I have no idea about virtualbox. I guess it might be related to bridging.