I write this post because after much turning I do not finish seeing why the containers have no communication, that is, from the containers abroad (for example, Debian repositories) and also from machines in the same range on the ESXi hosts to the containers have arrived, I leave a capture with several parts of the configuration.
This comes up quite often as an issue, its almost certainly due to the VMWare NIC not being configured to allow multiple MAC addresses. So its likely to need to be changed in the VMWare config for that VM.
I’m afraid I do not know, but I would imagine it would be in the network card settings in VMWare. Most likely something to do with either promiscuous mode or MAC filtering. Look for how to allow multiple MACs on a network card.
The problem is that you’re trying to bridge the VM guest’s interface to another bridge inside the VM, that in turn has one or more containers connected to it each with their own MAC addresses.
Often times the hypervisor will restrict the VM from sending packets from MAC addresses aside from the single MAC address that belongs to the VM guest.
Alternatively what can happen is that without enabling promiscuous mode, the VM guest will only get packets destined for its own MAC address and will not be able to get packets for containers running on it.
Good, I have taken but I answer, VMWare’s answer is basically what you have told me, so in the end what I did was route the traffic in a different segment and use a bridge.