Comment 31 for bug 1246236

I hit this problem today, and it turned out to be a non-MAAS bug.

I was trying to configure a Trusty host with VMware Workstation *and* LXCs sharing the same network.

It turns out that the combination of VMware plus Linux bridge interfaces have a bug: if I set up the VM network to be bridged to br0, I can ping hosts on the local network, and I can ping the Linux hypervisor, and I can ping any of the LXCs. I can even DHCP from the LXCs. But I *can't* establish any TCP connections to the LXCs from the VMware guest.

My current theory is that somehow the bridge interface is causing packets sentto the LXC from the VMware guest to be discarded at a low level, rather than sent up the stack. I couldn't find any IP Because when I configure VMware to bridge to a physical interface rather than a virtual bridge, it works. Until I disconnect the physical interface.

So the bottom line for me was:
(1) Have VMware bridge to the physical interface (in my case, it was eth0.100, a VLAN interface) if you want to use bridged mode
(2) Use a host-only network (without DHCP, so MAAS can do its thing!) if you want to develop in isolation, without sharing the network with the local LAN
 - Do NOT bridge VMware to a bridge created with 'brctl' or similar!

I added the VMware bridge interface (vmnet1) to the br0 interface I'm using for my MAAS LXC, which may get me the best of both. I'll continue to test this configuration.