caskd
/
entitydb
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated prefix allocation format

This commit is contained in:
Tristan B. Kildaire 2021-06-03 10:13:14 +02:00
parent 4a0779b67e
commit cda6e14ed6
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -6,16 +6,17 @@ EntityDB holds all network allocations and associated information.
Firstly create an entry by creating a directory with your unique username, `deavmi/` for example.
Inside there you place your network allocations as `deavmi/networkName1`, `deavmi/networkName2` etc.
### Networks
An entry for `deavmi/networkName1` looks like this:
ALl network declarations are created as seperate files per allocation within `deavmi/networks`. An example would be `deavmi/networks/deavmi.home.network` which must look like this:
```
Prefix=ffff::/90
PublicKey=dfkhjfdhjfhjkk
[deavmi.home.network]
# Required network information
Prefix="fdd2:cbf2:61bd::/48"
PublicKey=""
#Subnets within the /48 subnet
Networks=[]
```
Create a directory called `networkName/` and inside of it
# For network connectivity tests
RouterIP="fdd2:cbf2:61bd::1"
NonRouterIP="fdd2:cbf2:61bd::2"
```