sync/NeoNetwork
1
0
Fork 0
mirror of https://github.com/NeoCloud/NeoNetwork synced 2024-05-17 09:41:46 +08:00
Code Issues Releases Wiki Activity

README: up

Browse source
This commit is contained in:
Neo_Chen 2020-05-13 21:57:47 +08:00
parent 02d9739431
commit 5b1bf47a12
2 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -1,10 +1,8 @@
# NeoNetwork
A useless VPN network ready for peering!
**WARNING:** This network is not interconnected to DN42 yet
Git Repo. [here](https://git.neocloud.tw)
Pull requests are welcomed!
Working language: `zh_* / en_*`
Telegram Group invitation link available at TXT record of `join-telegram.neocloud.tw`
## IXs
@ -27,11 +25,12 @@ Any protocol supported by Bird, Quagga or FRRouting, BGP recommended.
All IPv4 addresses are under the range 10.127.0.0/16
All IPv6 addresses are under the range fd10:127::/32
see routes.txt for allocated domain.
see [route](https://github.com/NeoCloud/NeoNetwork/tree/master/route)
and [route6](https://github.com/NeoCloud/NeoNetwork/tree/master/route6) for allocated subnet.
## DNS
There's a bind9 server on dns.neocloud.tw (10.127.225.2), all domain names are under ".neo".
There's a bind9 server on dns.neocloud.tw (`10.127.225.2` and `fd10:127:5f37:59df::255:2`), all domain names are under ".neo".
## Connection Graph
@ -44,5 +43,6 @@ There's a bind9 server on dns.neocloud.tw (10.127.225.2), all domain names are u
entity/ Entitys
route/ Network subnet allocation
node/ Nodes
peer/ Peering status
vpn/ VPN configuration examples (Tinc & WireGuard)
dns/ Bind9 DNS zone files and example configuration

12
docs/index.html
View file

@ -11,11 +11,9 @@
<h1>NeoNetwork</h1>
<p>A useless VPN network ready for peering!<br/>
<strong>WARNING:</strong> This network is not interconnected to DN42 yet<br/>
Git Repo. <a href="https://git.neocloud.tw">here</a><br/>
Pull requests are welcomed!<br/>
Working language: <code>zh_* / en_*</code><br/>
Telegram Group invitation link available at TXT record of <code>join-telegram.neocloud.tw</code></p>
Working language: <code>zh_* / en_*</code></p>
<h2>IXs</h2>
@ -33,17 +31,18 @@ megumi.yukipedia.cf (10.127.30.1, ASN 4242421037)
<h2>Routing Protocols</h2>
<p>Any protocol supported by Quagga or FRRouting, recommended to use BGP.</p>
<p>Any protocol supported by Bird, Quagga or FRRouting, BGP recommended.</p>
<h2>IP Addresses</h2>
<p>All IPv4 addresses are under the range 10.127.0.0/16<br/>
All IPv6 addresses are under the range fd10:127::/32<br/>
see routes.txt for allocated domain.</p>
see <a href="https://github.com/NeoCloud/NeoNetwork/tree/master/route">route</a>
and <a href="https://github.com/NeoCloud/NeoNetwork/tree/master/route6">route6</a> for allocated subnet.</p>
<h2>DNS</h2>
<p>There&rsquo;s a bind9 server on dns.neocloud.tw (10.127.225.2), all domain names are under &ldquo;.neo&rdquo;.</p>
<p>There&rsquo;s a bind9 server on dns.neocloud.tw (<code>10.127.225.2</code> and <code>fd10:127:5f37:59df::255:2</code>), all domain names are under &ldquo;.neo&rdquo;.</p>
<h2>Connection Graph</h2>
@ -56,6 +55,7 @@ asn/ BGP AS Number allocation
entity/ Entitys
route/ Network subnet allocation
node/ Nodes
peer/ Peering status
vpn/ VPN configuration examples (Tinc &amp; WireGuard)
dns/ Bind9 DNS zone files and example configuration
</code></pre>