-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
thanks I found the culprit, and not because I didn't know what I was
doing.. the output from the macvtaps that I'm using here as network
interfaces was letting traffic from the hypervisor. But the problem
didn't arise due to it not being setup properly but rather a technical
limitation of the classical bridge which can't be moved into a separate
namespace.. If the macvtap could be moved to another namespace then this
problem could be prevented, but the particular underlying nic interface
holding the macvtap is not designed to be moved out of the root namespace.
- Bug#765582: linux-image-3.16-2-amd64: port 138 ... westlake
- Bug#765582: marked as done (linux-image-3.... Debian Bug Tracking System
- Bug#765582: closed by Ben Hutchings <b.... westlake
