| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <50AE36E0.8000307@dlhnet.de> Date: Thu, 22 Nov 2012 15:29:52 +0100 From: Peter Lieven <pl@...net.de> To: "qemu-devel@...gnu.org" <qemu-devel@...gnu.org>, netdev@...r.kernel.org Subject: tap devices not receiving packets from a bridge Hi, is anyone aware of a problem with the linux network bridge that in very rare circumstances stops a bridge from sending pakets to a tap device? My problem occurs in conjunction with vanilla qemu-kvm-1.2.0 and Ubuntu Kernel 3.2.0-34.53 which is based on Linux 3.2.33. I was not yet able to reproduce the issue, it happens in really rare cases. The symptom is that the tap does not have any TX packets. RX is working fine. I see the packets coming in at the physical interface on the host, but they are not forwarded to the tap interface. The bridge itself has learnt the mac address of the vServer that is connected to the tap interface. It does not help to toggle the bridge link status, the tap interface status or the interface in the vServer. It seems that problem occurs if a tap interface that has previously been used, but set to nonpersistent is set persistent again and then is by chance assigned to the same vServer (=same mac address on same bridge) again. Unfortunately it seems not to be reproducible. Maybe this sounds familiar to someone? Thank you, Peter -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists