haaio.blogg.se

Switch(config)# interface fastEthernet0/0 …or Cisco Layer 3 Switch… switch# configure terminal

Router(config-subif)# encapsulation dot1Q 20 Router(config)# interface fastEthernet 0/0.20 Router(config-subif)# encapsulation dot1Q 10 Router(config)# interface fastEthernet 0/0.10 Here’s the configuration if you happen to have a Cisco IOS router… router(config)# interface fastEthernet 0/0 Connection between the router and the Docker host is configured as 802.1Q trunk on the router with VLAN 10 and VLAN 20.Ĭonfigure VLAN 10 and VLAN 20 on your router. You have a Docker host with a single eth0 interface connected to a router. Multiple macvlans with VLANs configuration You can map each Docker host interface to a macvlan network, thus extending the Layer 2 domain from the VLAN into the macvlan network. This aligns perfectly with the Linux implementation of VLANs, where each VLAN on a 802.1Q trunk connection is terminated on a sub-interface of the physical interface. Fortunately, a Docker host sub-interface can serve as a parent interface for the macvlan network. One macvlan, one Layer 2 domain and one subnet per physical interface, however, is a rather serious limitation in a modern virtualization solution. If you have read my introduction to macvlans and tried the basic macvlan bridge mode network configuration you are aware that a single Docker host network interface can serve as a parent interface to one macvlan or ipvlan network only.