From 8b8107e3b76a22e1b3dbf74a9bc3823b4d27cc3e Mon Sep 17 00:00:00 2001 From: "D. Domig" Date: Wed, 22 May 2019 20:56:34 +0200 Subject: [PATCH] Fix typos (#8650) --- network/macvlan.md | 37 +++++++++++++++++++------------------ 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/network/macvlan.md b/network/macvlan.md index e0f6c4013d..42b441d7e7 100644 --- a/network/macvlan.md +++ b/network/macvlan.md @@ -1,5 +1,5 @@ --- -title: Use Macvlan networks +title: Use macvlan networks description: All about using macvlan to make your containers appear like physical machines on the network keywords: network, macvlan, standalone redirect_from: @@ -13,25 +13,27 @@ this type of situation, you can use the `macvlan` network driver to assign a MAC address to each container's virtual network interface, making it appear to be a physical network interface directly connected to the physical network. In this case, you need to designate a physical interface on your Docker host to use for -the Macvlan, as well as the subnet and gateway of the Macvlan. You can even -isolate your Macvlan networks using different physical network interfaces. +the `macvlan`, as well as the subnet and gateway of the `macvlan`. You can even +isolate your `macvlan` networks using different physical network interfaces. Keep the following things in mind: - It is very easy to unintentionally damage your network due to IP address exhaustion or to "VLAN spread", which is a situation in which you have an inappropriately large number of unique MAC addresses in your network. + - Your networking equipment needs to be able to handle "promiscuous mode", where one physical interface can be assigned multiple MAC addresses. + - If your application can work using a bridge (on a single Docker host) or overlay (to communicate across multiple Docker hosts), these solutions may be better in the long term. ## Create a macvlan network -When you create a Macvlan network, it can either be in bridge mode or 802.1q +When you create a `macvlan` network, it can either be in bridge mode or 802.1q trunk bridge mode. -- In bridge mode,Macvlan traffic goes through a physical device on the host. +- In bridge mode, `macvlan` traffic goes through a physical device on the host. - In 802.1q trunk bridge mode, traffic goes through an 802.1q sub-interface which Docker creates on the fly. This allows you to control routing and @@ -39,7 +41,7 @@ trunk bridge mode. ### Bridge mode -To create a Macvlan network which bridges with a given physical network +To create a `macvlan` network which bridges with a given physical network interface, use `--driver macvlan` with the `docker network create` command. You also need to specify the `parent`, which is the interface the traffic will physically go through on the Docker host. @@ -47,18 +49,18 @@ physically go through on the Docker host. ```bash $ docker network create -d macvlan \ --subnet=172.16.86.0/24 \ - --gateway=172.16.86.1 \ + --gateway=172.16.86.1 \ -o parent=eth0 pub_net ``` -If you need to exclude IP addresses from being used in the Macvlan network, such +If you need to exclude IP addresses from being used in the `macvlan` network, such as when a given IP address is already in use, use `--aux-addresses`: ```bash -$ docker network create -d macvlan \ - --subnet=192.168.32.0/24 \ +$ docker network create -d macvlan \ + --subnet=192.168.32.0/24 \ --ip-range=192.168.32.128/25 \ - --gateway=192.168.32.254 \ + --gateway=192.168.32.254 \ --aux-address="my-router=192.168.32.129" \ -o parent=eth0 macnet32 ``` @@ -70,7 +72,7 @@ Docker interprets that as a sub-interface of `eth0` and creates the sub-interfac automatically. ```bash -$ docker network create -d macvlan \ +$ docker network create -d macvlan \ --subnet=192.168.50.0/24 \ --gateway=192.168.50.1 \ -o parent=eth0.50 macvlan50 @@ -85,26 +87,25 @@ instead, and get an L2 bridge. Specify `-o ipvlan_mode=l2`. $ docker network create -d ipvlan \ --subnet=192.168.210.0/24 \ --subnet=192.168.212.0/24 \ - --gateway=192.168.210.254 \ - --gateway=192.168.212.254 \ + --gateway=192.168.210.254 \ + --gateway=192.168.212.254 \ -o ipvlan_mode=l2 ipvlan210 ``` ## Use IPv6 If you have [configured the Docker daemon to allow IPv6](/config/daemon/ipv6.md), -you can use dual-stack IPv4/IPv6 Macvlan networks. +you can use dual-stack IPv4/IPv6 `macvlan` networks. ```bash -$ docker network create -d macvlan \ +$ docker network create -d macvlan \ --subnet=192.168.216.0/24 --subnet=192.168.218.0/24 \ - --gateway=192.168.216.1 --gateway=192.168.218.1 \ + --gateway=192.168.216.1 --gateway=192.168.218.1 \ --subnet=2001:db8:abc8::/64 --gateway=2001:db8:abc8::10 \ -o parent=eth0.218 \ -o macvlan_mode=bridge macvlan216 ``` - ## Next steps - Go through the [macvlan networking tutorial](/network/network-tutorial-macvlan.md)