From 6a47c70d60f5ac92b152e1c8ef7fe5b714fe7833 Mon Sep 17 00:00:00 2001 From: Wolfgang Powisch Date: Wed, 1 Apr 2015 00:21:21 +0200 Subject: [PATCH] Update networking.md Signed-off-by: Wolfgang Powisch --- docs/sources/articles/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/articles/networking.md b/docs/sources/articles/networking.md index 754d9989c3..b3d2bdace1 100644 --- a/docs/sources/articles/networking.md +++ b/docs/sources/articles/networking.md @@ -652,7 +652,7 @@ for Docker. When adding a third host you would add a route for the subnet Remember the subnet for Docker containers should at least have a size of `/80`. This way an IPv6 address can end with the container's MAC address and you prevent NDP neighbor cache invalidation issues in the Docker layer. So if you -have a `/64` for your whole environment use `/68` subnets for the hosts and +have a `/64` for your whole environment use `/78` subnets for the hosts and `/80` for the containers. This way you can use 4096 hosts with 16 `/80` subnets each.