Configuring IPv6-Only and Dual-Stack IPv4/IPv6 Networks with IPvlan

it also gives you total control over IPv6 addressing as well as feature parity between the two address families. - The next example will start with IPv6 only. Start two containers on the same VLAN `139` and ping one another. Since the IPv4 subnet is not specified, the default IPAM will provision a default IPv4 subnet. That subnet is isolated unless the upstream network is explicitly routing it on VLAN `139`. ```console # Create a v6 network $ docker network create -d ipvlan \ --ipv6 --subnet=2001:db8:abc2::/64 --gateway=2001:db8:abc2::22 \ -o parent=eth0.139 v6ipvlan139 # Start a container on the network $ docker run --net=v6ipvlan139 -it --rm alpine /bin/sh ``` View the container eth0 interface and v6 routing table: ```console # Inside the IPv6 container $$ ip a show eth0 75: eth0@if55: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default link/ether 00:50:56:2b:29:40 brd ff:ff:ff:ff:ff:ff inet 172.18.0.2/16 scope global eth0 valid_lft forever preferred_lft forever inet6 2001:db8:abc4::250:56ff:fe2b:2940/64 scope link valid_lft forever preferred_lft forever inet6 2001:db8:abc2::1/64 scope link nodad valid_lft forever preferred_lft forever $$ ip -6 route 2001:db8:abc4::/64 dev eth0 proto kernel metric 256 2001:db8:abc2::/64 dev eth0 proto kernel metric 256 default via 2001:db8:abc2::22 dev eth0 metric 1024 ``` Start a second container and ping the first container's v6 address. ```console # Test L2 connectivity over IPv6 $ docker run --net=v6ipvlan139 -it --rm alpine /bin/sh # Inside the second IPv6 container $$ ip a show eth0 75: eth0@if55: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default link/ether 00:50:56:2b:29:40 brd ff:ff:ff:ff:ff:ff inet 172.18.0.3/16 scope global eth0 valid_lft forever preferred_lft forever inet6 2001:db8:abc4::250:56ff:fe2b:2940/64 scope link tentative dadfailed valid_lft forever preferred_lft forever inet6 2001:db8:abc2::2/64 scope link nodad valid_lft forever preferred_lft forever $$ ping6 2001:db8:abc2::1 PING 2001:db8:abc2::1 (2001:db8:abc2::1): 56 data bytes 64 bytes from 2001:db8:abc2::1%eth0: icmp_seq=0 ttl=64 time=0.044 ms 64 bytes from 2001:db8:abc2::1%eth0: icmp_seq=1 ttl=64 time=0.058 ms 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.044/0.051/0.058/0.000 ms ``` The next example with setup a dual stack IPv4/IPv6 network with an example VLAN ID of `140`. Next create a network with two IPv4 subnets and one IPv6 subnets, all of which have explicit gateways: ```console $ docker network create -d ipvlan \ --subnet=192.168.140.0/24 --subnet=192.168.142.0/24 \ --gateway=192.168.140.1 --gateway=192.168.142.1 \ --subnet=2001:db8:abc9::/64 --gateway=2001:db8:abc9::22 \ -o parent=eth0.140 \ -o ipvlan_mode=l2 ipvlan140 ``` Start a container and view eth0 and both v4 & v6 routing tables: ```console $ docker run --net=ipvlan140 --ip6=2001:db8:abc2::51 -it --rm alpine /bin/sh $ ip a show eth0 78: eth0@if77: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default link/ether 00:50:56:2b:29:40 brd ff:ff:ff:ff:ff:ff inet 192.168.140.2/24 scope global eth0 valid_lft forever preferred_lft forever inet6 2001:db8:abc4::250:56ff:fe2b:2940/64 scope link valid_lft forever preferred_lft forever inet6 2001:db8:abc9::1/64 scope link nodad valid_lft forever preferred_lft forever $$ ip route default via 192.168.140.1 dev eth0 192.168.140.0/24 dev eth0 proto kernel scope link src 192.168.140.2 $$ ip -6 route 2001:db8:abc4::/64 dev eth0 proto kernel metric 256 2001:db8:abc9::/64 dev eth0 proto kernel metric 256 default via 2001:db8:abc9::22 dev eth0 metric 1024 ``` Start a second container with a specific `--ip4` address and ping the first host using IPv4 packets: ```console $ docker run --net=ipvlan140 --ip=192.168.140.10 -it --rm alpine /bin/sh

This section demonstrates how to create and configure IPv6-only networks and dual-stack IPv4/IPv6 networks using IPvlan in Docker. It includes examples of creating a v6 network, starting containers on the network, viewing the container's eth0 interface and v6 routing table, and pinging between containers using IPv6. Additionally, it details the creation of a network with multiple IPv4 and IPv6 subnets, specifying gateways for each, and demonstrates how to start containers with specific IPv4 and IPv6 addresses, showcasing the ability to ping between containers using IPv4.