Re: kern/46199: 6.0_BETA. "qemu -net tap" + bridge(4). Network problems in guests.

[Aleksey Cheusov <cheusov%tut.by@localhost>]

The following reply was made to PR kern/46199; it has been noted by GNATS.

From: Aleksey Cheusov <cheusov%tut.by@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost, 
gnats-admin%netbsd.org@localhost, 
        netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/46199: 6.0_BETA. "qemu -net tap" + bridge(4). Network
 problems in guests.
Date: Fri, 23 Mar 2012 18:31:50 +0300

 On Thu, Mar 15, 2012 at 6:00 PM, Manuel Bouyer 
<bouyer%antioche.eu.org@localhost> wro=
 te:
 > On Thu, Mar 15, 2012 at 12:55:02PM +0000, Aleksey Cheusov wrote:
 >> =A0I'm not sure I understood your question. But Opkts sremains the same,
 >> =A0a number of drops increased significantly, Ipkts increased a little b=
 it.
 >>
 >> =A0tap3 =A01500 =A0<Link> =A0 =A0 =A0 =A0f2:0b:a4:c7:dd:00 =A0 =A0 1124 =
 =A0 =A0 0 =A0 =A028722
 >> =A0 0 =A0 =A0 0 201213
 >> =A0tap3 =A01500 =A0fe80::/64 =A0 =A0 fe80::f00b:a4ff:f =A0 =A0 1124 =A0 =
 =A0 0 =A0 =A028722
 >> =A0 0 =A0 =A0 0 201213
 >
 > BTW, could you see if the affected tap device has OACTIVE flag set when
 > in this state ?
 
 Yes, OACTIVE flag is set on "dead" tap3.
 
 Also, I've got an idea that my ipf rules may cause this problem.
 When I disabled them I could not reproduce the problem,
 at least two virtual machines worked for a day without problems.
 I'm not sure this is relevant, though.