FAQ.md
... ...
@@ -1,6 +1,6 @@
1 1
## How do I connect to DN42?
2 2
3
-We have a [page](/howto/Getting-started) for that!
3
+We have a [page](/howto/Getting-Started) for that!
4 4
5 5
6 6
### What BGP daemon should I use?
contact.md
... ...
@@ -2,7 +2,7 @@
2 2
3 3
Members of the dn42 network mostly communicate via IRC or the mailing list.
4 4
5
-If you would like to contact an individual network operator, you will find contact information in the [Whois](/Whois) registry.
5
+If you would like to contact an individual network operator, you will find contact information in the [Whois](/services/Whois) registry.
6 6
7 7
## Mailing list
8 8
... ...
@@ -15,7 +15,7 @@ If you would like to contact an individual network operator, you will find conta
15 15
16 16
Channel #dn42 in [hackint](http://www.hackint.eu/)
17 17
18
-See [IRC](/IRC) too.
18
+See [IRC](/services/IRC) too.
19 19
20 20
## Telegram
21 21
howto/EdgeOS-Config.md
... ...
@@ -11,8 +11,8 @@ This document describes some possibilities for connecting to dn42 using an Ubiqu
11 11
12 12
## First Steps
13 13
14
-1. Create the required objects in the Registry - see [Getting Started](/Getting-Started)
15
-2. Find a peer - ask nicely in [IRC](/IRC)!
14
+1. Create the required objects in the Registry - see [Getting Started](/howto/Getting-Started)
15
+2. Find a peer - ask nicely in [IRC](/services/IRC)!
16 16
3. Get the following details:
17 17
* Tunnel configuration (OpenVPN, IPsec, QuickTun)
18 18
* AS numbers
howto/GRE-plus-IPsec.md
... ...
@@ -25,10 +25,10 @@
25 25
* At least one peer should operate his own (Sub-)CA.
26 26
27 27
## How to configure a GRE tunnel on FreeBSD
28
-See [GRE on FreeBSD](gre-on-freebsd).
28
+See [GRE on FreeBSD](GRE-on-FreeBSD).
29 29
30 30
## How to configure IPsec on FreeBSD
31
-See [IPsec on FreeBSD](ipsec-on-freebsd).
31
+See [IPsec on FreeBSD](IPsec-on-FreeBSD).
32 32
33 33
## How to configure GRE + IPsec on Debian
34
-See [GRE + IPsec on Debian](gre-plus-ipsec-debian).
34
+See [GRE + IPsec on Debian](IPsecWithPublicKeys/GRE-plus-IPsec-Debian).
howto/Getting-Started.md
... ...
@@ -313,9 +313,9 @@ There is some documentation in this wiki, like [gre-plus-ipsec](GRE-plus-IPsec).
313 313
314 314
## Running a routing daemon
315 315
316
-You need a routing daemon to speak BGP with your peers. People usually run Quagga or Bird, but you may use anything (OpenBGPD, XORP, somebody even used an old [hardware router](bgp-on-extreme-summit1i) ). See the relevant [FAQ entry](/FAQ#frequently-asked-questions_what-bgp-daemon-should-i-use).
316
+You need a routing daemon to speak BGP with your peers. People usually run Quagga or Bird, but you may use anything (OpenBGPD, XORP, somebody even used an old [hardware router](BGP-on-Extreme-Summit1i) ). See the relevant [FAQ entry](/FAQ#frequently-asked-questions_what-bgp-daemon-should-i-use).
317 317
318
-You can find [configuration examples for Bird here](bird).
318
+You can find [configuration examples for Bird here](Bird).
319 319
320 320
## Configuration Examples
321 321
... ...
@@ -337,7 +337,7 @@ You can find [configuration examples for Bird here](bird).
337 337
338 338
# Configure DNS
339 339
340
-See [Services DNS](/Services/DNS).
340
+See [Services DNS](/services/DNS).
341 341
342 342
# Use and provide services
343 343
howto/IPsecWithPublicKeys/RacoonExample.md
... ...
@@ -1,6 +1,6 @@
1 1
Quote from #dn42: `hexa: nobody runs racoon on their free will :)`.
2 2
3
-See also [strongswan](howto/IPsecWithPublicKeys/strongSwan5Example)
3
+See also [strongSwan](/howto/IPsecWithPublicKeys/strongSwan5Example)
4 4
5 5
The keys are generated with plainrsa-gen.
6 6
... ...
@@ -40,4 +40,4 @@ remote 192.168.255.2 {
40 40
41 41
## Se also
42 42
43
-[debian specific configuration](IPsecWithPublicKeys/GRE plus IPsec Debian)
43
+[Debian specific configuration](/howto/IPsecWithPublicKeys/GRE-plus-IPsec-Debian)
howto/IPv6.md
... ...
@@ -16,7 +16,7 @@ If you're already running IPv4 on DN42, here's how to get started:
16 16
* ???
17 17
* Profit!
18 18
19
-If not, you can follow the instructions on the [Getting Started](GettingStarted) page, as they'll mostly apply to IPv6 aswell.
19
+If not, you can follow the instructions on the [Getting Started](Getting-Started) page, as they'll mostly apply to IPv6 aswell.
20 20
21 21
## What can i do on DN42-v6 ?
22 22
services/DNS.md
... ...
@@ -65,5 +65,5 @@ Authoritative DNS for DN42 is provided by the *.delegation-servers.dn42 servers,
65 65
* [dns/Configuration](/services/dns/Configuration) - Forwarder/Resolver configuration examples
66 66
* [New DNS](/services/New-DNS) - current architecture
67 67
* [dns/External-DNS](/services/dns/External-DNS) - external DNS zones from interconnected networks
68
-* [Old Hierarchical DNS](/Old-Hierarchical-DNS) - deprecated
69
-* [Original DNS (deprecated)](/Original-DNS-(deprecated)) - deprecated
68
+* [Old Hierarchical DNS](/services/Old-Hierarchical-DNS) - deprecated
69
+* [Original DNS (deprecated)](/services/Original-DNS-(deprecated)) - deprecated
services/Distributed-Wiki.md
... ...
@@ -1,7 +1,7 @@
1 1
# this page is outdated and need update
2 2
3 3
The idea is to deploy mirrors across dn42 using [anycast](https://en.wikipedia.org/wiki/Anycast) addressing (BGP), thus providing redundancy, load-balancing and improved access times to the wiki. Sites are powered by [gollum](https://github.com/gollum/gollum) which has no native SSL support, so Nginx acts as a reverse proxy and handles the encryption.
4
-The local webserver is monitored with a simple [shell script](/Distributed-Wiki#exabgp_watchdog-script) working [in conjunction](/Distributed-Wiki#exabgp) with [ExaBGP](https://github.com/Exa-Networks/exabgp), announcing/withdrawing the assigned route if the service is up/down.
4
+The local webserver is monitored with a simple [shell script](Distributed-Wiki#exabgp_watchdog-script) working [in conjunction](Distributed-Wiki#exabgp) with [ExaBGP](https://github.com/Exa-Networks/exabgp), announcing/withdrawing the assigned route if the service is up/down.
5 5
6 6
## Prerequisites
7 7
services/IPv6-Anycast.md
... ...
@@ -18,7 +18,7 @@ Remember, if you announce an anycast /64, then you need to provide **all** servi
18 18
| internal Wiki | `fd42:d42:d42:80::1/64` | TCP/80, TCP/443 | |
19 19
20 20
21
-[Providers]: Providing-Anycast-DNS#Persons-providing-anycast-DNS-for-IPv6
21
+[Providers]: dns/Providing-Anycast-DNS#Persons-providing-anycast-DNS-for-IPv6
22 22
23 23
### Future services
24 24
services/New-DNS.md
... ...
@@ -1,4 +1,4 @@
1
-After frequent issues with the [Old Hierarchical DNS](/Old-Hierarchical-DNS) system in early 2018, work has started to build a new and more reliable DNS system. The main goals are:
1
+After frequent issues with the [Old Hierarchical DNS](Old-Hierarchical-DNS) system in early 2018, work has started to build a new and more reliable DNS system. The main goals are:
2 2
* Reliability and Consistency to avoid debugging very obscure issues that are also hard to reproduce.
3 3
* Low maintenance burden on operators.
4 4
* Proper DNSSEC support for everything.
... ...
@@ -47,6 +47,6 @@ The set of valid KSKs can be found in the registry.
47 47
48 48
# See also
49 49
50
-* [DNS Quick Start](/DNS)
51
-* [Old Hierarchical DNS](/Old-Hierarchical-DNS)
52
-* [Original DNS (deprecated)](/Original-DNS-(deprecated))
50
+* [DNS Quick Start](DNS)
51
+* [Old Hierarchical DNS](Old-Hierarchical-DNS)
52
+* [Original DNS (deprecated)](Original-DNS-(deprecated))
services/Old-Hierarchical-DNS.md
... ...
@@ -1,4 +1,4 @@
1
-This information is now **deprecated**. Please check [New DNS](/New DNS) for the current architecture.
1
+This information is now **deprecated**. Please check [New DNS](New-DNS) for the current architecture.
2 2
3 3
***
4 4
services/Original-DNS-(deprecated).md
... ...
@@ -1,5 +1,5 @@
1 1
# Original DNS (deprecated)
2
-This information is now **deprecated**. Please check [New DNS](/New DNS) for the current architecture.
2
+This information is now **deprecated**. Please check [New DNS](New-DNS) for the current architecture.
3 3
4 4
***
5 5
... ...
@@ -23,7 +23,7 @@ If you run your own resolver (`unbound`, `dnsmasq`, `bind`), you can configure i
23 23
24 24
### Recursive resolver
25 25
26
-You may also want to configure your resolver to recursively resolve dn42 domains. For this, you need to find authoritative DNS servers for the `dn42` zone (and for the reverse zones). See [services/dns/Recursive DNS resolver](/services/dns/Recursive DNS resolver).
26
+You may also want to configure your resolver to recursively resolve dn42 domains. For this, you need to find authoritative DNS servers for the `dn42` zone (and for the reverse zones). See [services/dns/Recursive DNS resolver](/services/dns/Recursive-DNS-resolver).
27 27
28 28
### Building the dn42 zones from the registry
29 29
... ...
@@ -35,12 +35,12 @@ The root zone for `dn42.` is built from the [whois registry](/services/Whois). I
35 35
36 36
## DNS services for other networks
37 37
38
-Other networks are interconnected with dn42 (ChaosVPN, Freifunk, etc). Some of them also provide DNS service, you can configure your resolver to use it. See [External DNS](/External DNS).
38
+Other networks are interconnected with dn42 (ChaosVPN, Freifunk, etc). Some of them also provide DNS service, you can configure your resolver to use it. See [External DNS](dns/External-DNS).
39 39
40 40
## Providing DNS services
41 41
42
-See [Providing Anycast DNS](/Providing Anycast DNS).
42
+See [Providing Anycast DNS](dns/Providing-Anycast-DNS).
43 43
44
-## [Old Hierarchical DNS](/Old Hierarchical DNS)
44
+## [Old Hierarchical DNS](Old-Hierarchical-DNS)
45 45
46 46
This is a new effort to build a DNS system that mirrors how DNS was designed to work in clearnet.
services/Whois.md
... ...
@@ -32,7 +32,7 @@ Note that currently, most AS are using one of the legacy ASN range (and will pro
32 32
33 33
## DNS zones
34 34
35
-dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](/DNS).
35
+dn42 uses the `dn42.` TLD, which is not present in the root DNS zone of the ICANN-net. For details, see [DNS](DNS).
36 36
37 37
Note that other TLDs should also be usable from dn42, most notably from Freifunk and ChaosVPN. A tentative list is available at [External DNS](/services/dns/External-DNS).
38 38
... ...
@@ -57,7 +57,7 @@ The service is provided by [dn42regsrv](https://git.dn42.us/burble/dn42regsrv) w
57 57
58 58
## Authentication
59 59
60
-See the page on [Registry Authentication](howto/Registry-Authentication)
60
+See the page on [Registry Authentication](/howto/Registry-Authentication)
61 61
62 62
# DNS interface
63 63
services/dns/Providing-Anycast-DNS.md
... ...
@@ -10,7 +10,7 @@ Configuration requirements for all members of the anycast group are:
10 10
* listen on a unicast IP too for testing/debugging reasons
11 11
* with bind, please use ```minimal-responses yes;``` (goes into ```options```/```view```)
12 12
13
-It is _really_ good to hang around in [IRC](/IRC) to get things sorted out, if something doesn't work. Letting some people test your DNS behavior before joining the anycast-group is considered best practice - better safe than sorry.
13
+It is _really_ good to hang around in [IRC](/services/IRC) to get things sorted out, if something doesn't work. Letting some people test your DNS behavior before joining the anycast-group is considered best practice - better safe than sorry.
14 14
15 15
* **IP:** 172.23.0.53
16 16
* **Announciation Subnet:** 172.23.0.53/32
services/dns/Recursive-DNS-resolver.md
... ...
@@ -1,6 +1,6 @@
1 1
If you want to run your own recursive DNS server, you must find upstream servers that are authoritative for the dn42 zones.
2 2
3
-You may use some servers listed in the [table of anycast servers](/Providing-Anycast-DNS#Persons-providing-anycast-DNS), or just use `172.22.119.160` and `172.22.119.163` (ns{1,2}.fritz.dn42).
3
+You may use some servers listed in the [table of anycast servers](Providing-Anycast-DNS#Persons-providing-anycast-DNS), or just use `172.22.119.160` and `172.22.119.163` (ns{1,2}.fritz.dn42).
4 4
5 5
## Configuration
6 6