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.
On 16/10/14 09:39 AM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the systemd package:
#765584: systemd: port 138 traffic generated
It has been closed by Michael Biebl <bi...@debian.org>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Michael Biebl
<bi...@debian.org> by
replying to this email.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
