Note 1: as far as I understand the suggested MACVLAN architecture, I cannot use two physical network interfaces with the same MACVLAN. However, in my application I need to have a single LAN/L2 domain spanning an eth0 LAN, as well as a wlan0 AP-mode LAN.
Note 2: MACVLAN in Bridge Mode has another show stopper for my use case; when the physical interface goes down, so go down all sub-interfaces. My network function containers then would be unable to do their work at all, which is bad, as the need to communicate with each other, not only to the external LAN.
My situation: for a project I have a set of Docker containers that work as full-blown IP nodes, especially when it comes to IPv6. These containers are to be wired up to a Docker "bridge" network inside the host, say br0, using a stock Linux kernel Ethernet bridge. This bridge br0 will get a direct port to the outside LAN via an enslaved host network interface, say eth0 (host!). In addition, br0 has an (optional) wlan0 AP enslaved port. N.B: It's okay that the host will be reachable via br0.
Now I want to create this Docker bridge network without any NAT/masquerading going from br0 to any of the host's (other) network interfaces. And I don't want and don't need any DHCPv4 server and DNS proxy getting installed on the br0 network. In fact, as br0 has an enslaved eth0 and wlan0 to the outside LAN, there must not get any auxiliary Docker network services instantiated.
How can I tell Docker to create a plain simple bridge network without any IP address management, without DNS services, and without NAT? Is this even possible using only the stock bridge network driver?
