From 9c5954faecb9147204bf7675ebe82bfa17822cd1 Mon Sep 17 00:00:00 2001 From: Neo_Chen Date: Wed, 6 May 2020 19:46:24 +0800 Subject: [PATCH] document: route-dir: up --- document/{route-dir.en_US.txt => route-dir.txt} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename document/{route-dir.en_US.txt => route-dir.txt} (83%) diff --git a/document/route-dir.en_US.txt b/document/route-dir.txt similarity index 83% rename from document/route-dir.en_US.txt rename to document/route-dir.txt index d8668f4..3e37fd5 100644 --- a/document/route-dir.en_US.txt +++ b/document/route-dir.txt @@ -5,9 +5,9 @@ According to the common usage of this VPN network, the IP allocation can be classified into the following rules, with its format normalized, as the file name of the routing distribution definition file: -1. Point-to-Point /30 Tunnel: `10.127.0.x/30` （where x is divisible by 4） -2. Contiguous Subnet: `10.127.x.y/z` (where z must be greater than 16） -3. Peer-to-Peer: `PTP,10.127.x.x~10.127.x.x` （IP on both sides is /32） +1. /30 Tunnel: `10.127.0.x/30` （where x is divisible by 4） +2. Normal Subnet: `10.127.x.y/z` (where z must be greater than 16） +3. Point-to-Point: `PTP,10.127.x.x~10.127.x.x` （IP on both sides is /32） 4. Loopback Address: `10.127.255.x/32` Definition Format @@ -16,7 +16,7 @@ Definition Format The content of the file can be divided into the following fields. To simplify processing, Shell Script variable definition syntax will be used as the syntax of the definition file. In addition, variables must -be defined in the same order as the following: +be present if it's not optional and defined in the same order as the following: TYPE= PROTO= (only for peer-to-peer /30 tunnels and peer-to-peer /32 peers)