Re: macvlan device blocks traffic for 30 secs

[Patrick McHardy <kaber@trash.net>]

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?