From 3e1512873ad1fa7ad60a295ef86cefd3ac8c25f8 Mon Sep 17 00:00:00 2001 From: John-Paul Robinson Date: Fri, 24 Aug 2018 15:18:56 -0500 Subject: [PATCH] Fix the RFC and private internet network address It seems the RFC should be 1918 which defines IP addresses for private networks. The existing RFC 5737 actually defines private IP ranges for use in documentation. Change-Id: Ic794585e636bb9a9c915347a801c8a4f0baa9012 Closes-Bug: 1788936 --- doc/source/admin/intro-nat.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/admin/intro-nat.rst b/doc/source/admin/intro-nat.rst index d700a1d746c..186f695d0b0 100644 --- a/doc/source/admin/intro-nat.rst +++ b/doc/source/admin/intro-nat.rst @@ -27,12 +27,12 @@ address of the sender in IP packets. SNAT is commonly used to enable hosts with *private addresses* to communicate with servers on the public Internet. -`RFC 5737 `_ +`RFC 1918 `_ reserves the following three subnets as private addresses: -* ``192.0.2.0/24`` -* ``198.51.100.0/24`` -* ``203.0.113.0/24`` +* ``10.0.0.0/8`` +* ``172.16.0.0/12`` +* ``192.168.0.0/16`` These IP addresses are not publicly routable, meaning that a host on the public Internet can not send an IP packet to any of these addresses. Private IP