Changes in 5169f6c: Updated FAQ (markdown)

FAQ.md

@@ -2,43 +2,46 @@

 [[_TOC_]]

-### Why are you using monotone for the registry? Why not Git?

+### How do I connect to DN42 ?

-There is an important difference between the data model of monotone and Git: In Git branches *are* heads, while in monotone, branches are a list of heads. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In Git, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.

+We have a [page](/howto/Getting-started) for that !

-The DN42 registry is stored on multiple monotone servers which sync with each other. This is not possible in Git, because the Git servers don't know how to handle merge conflicts. In monotone, the servers just sync the conflict.

+### What BGP daemon should I use?

+This is really up to you: that's the magic of open protocols.

-### What about IPv6 in dn42?

+Many users run Bird or FRRouting in a VPS, but there is a variety of BGP implementations in use across the network and some networks even run hardware routers or experimental software. DN42 is a great place to try out and get familiar with your implementation of choice in a live network. 

-There are some ASes in dn42 that route IPv6 traffic. They generally use the "Unique Local Address" range (ULA, *fd00::/8*) defined by [RFC 4193](https://tools.ietf.org/html/rfc4193). A minor disadvantage of using ULAs is that you need to announce two prefixes in your LAN if you want to use stateless autoconfiguration and no NAT: The ULA and a globally routed prefix. Usually, this works fine, but it may cause issues with legacy clients which don't implement [RFC 6172](https://tools.ietf.org/html/rfc6172) correctly.

+### Can I connect to DN42 from home through my ISP ?

-To get your own ULA range, simply pick a **random** prefix of the form fdXX:XXXX:XXXX/48 and enter it into the dn42 registry to make sure there are no collisions.

+Sure. As long as you have a 24/7 connection, can configure VPN tunnels and run BGP then you can connect to DN42. Do let your peers know if you have a dynamic IP address and you may also want to consider preventing transit traffic through your network if you have a relatively slow connection.

-In theory, globally routable IPv6 networks could also be used inside dn42. However, this would complicate prefix filtering for everybody, and might lead to strange routing patterns, where packets are routed partially on dn42 and partially through the Internet. Most dn42 ASes filter such IPv6 prefixes, which means you'd have a hard time making them reachable in dn42.

+Many users do use a virtual private server (VPS) for connecting to DN42. A VPS is a relatively cheap option that is always on and which (typically) provides a faster, more stable connection than your home. VPS have another advantage that if you mess something up, you won't break your home access to the internet. 

-At the moment, it is safe to assume that everyone doing IPv6 routing accepts at least prefixes from fd00::/8 with prefix lengths between 48 and 64 bits (inclusive) if they are part of the registry.

+### Does the registry use monotone or git ?

+The DN42 registry used to be maintained in monotone, but was moved to git following resource and performance

+issues. There may still be references back to monotone in some of the documentation, but the registry location is now:

-### Why are you using ASN in the 76100-76199 range?

+https://git.dn42.us/dn42/registry

-Yes, we know that this is not private ASN space (rather, it is part of the reserved block 65552-131071, see [IANA](http://www.iana.org/assignments/as-numbers/as-numbers.xhtml)).

-We used to assign ASN in the 64600-64855 range, where you would get ASN 64600+X if you had 172.22.X.0/24. Since we are now assigning /25 by default, and we have extended the address range to include 172.23.0.0/16, this is legacy.

+### What about IPv6 in dn42?

-Another issue with the private ASN range 64512-65534: other projects are also using it (for instance, Freifunk, Anonet, etc), which can lead to conflicts.

+DN42 supports IPv6 and some users do run IPv6 only networks. DN42 uses the "Unique Local Address" range (ULA, *fd00::/8*) defined by [RFC 4193](https://tools.ietf.org/html/rfc4193). 

-Fortunately, [RFC6996](http://tools.ietf.org/html/rfc6996) defines a new private ASN range: 4200000000-4294967294. Given the size of this range, there is little chance of running into a conflict.

+Globally routable IPv6 prefixes are not supported in DN42; whilst in theory they could be announced, most networks will reject the prefixes and some networks will filter traffic to the ULA range only. 

-We now encourage dn42 users to use the newly-allocated ranges in **4242420000-4242429999**. See the [registry page](Services/Whois#AS-numbers) for details.

+### Why are you using ASN in the 76100-76199 range?

+DN42 now uses ASNs in the 4242420000-4242429999 range, but the 76100-76199 range was used historically, and there are still a very small number of networks using legacy ASNs that have not migrated. 

-### What BGP daemon should I use?

+Previously, DN42 has used a two other ASN ranges:

-This is really up to you: that's the magic of open protocols.

+We used to assign ASN in the 64600-64855 range, where you would get ASN 64600+X if you had 172.22.X.0/24. Once the address range was extended to include additional blocks, this process was obsoleted. Another issue with the private ASN range 64512-65534 was that other projects are also using it (for instance, Freifunk, Anonet, etc), which can lead to conflicts. 

-As of 2014, most people seem to use either Quagga or Bird (with a growing preference for Bird). You may also encounter users of OpenBGPd. Even more occasionally, people use hardware BGP routers in dn42, for instance [Extreme Networks](howto/bgp-on-extreme-summit1i) hardware.

+Prior to using ASNs in the new private ASN range 4200000000-4294967294 ([RFC6996](http://tools.ietf.org/html/rfc6996)) Some ASNs were allocated from the [ASN reserved block](http://www.iana.org/assignments/as-numbers/as-numbers.xhtml) in the 76100-76199 range. 

 ### Can I update the wiki?

-Yes, but only when connecting to this site via dn42 over SSL.

\ No newline at end of file

+Yes, the wiki can be edited when browsing to [wiki.dn42](https://wiki.dn42).

\ No newline at end of file

_Footer.md

...	...	@@ -1 +1 @@
1		-Hosted by: [xuu](mailto:[email protected]), [nurtic-vibe](mailto:[email protected]), [toBee](mailto:[email protected]), [burble](mailto:[email protected]) \| Accessible via: [dn42](http://wiki.dn42), [tor](http://jsptropkiix3ki5u.onion), [i2p](http://beb6v2i4jevo72vvnx6segsk4zv3pu3prbwcfuta3bzrcv7boy2q.b32.i2p/)
...	...	\ No newline at end of file
	0	+Hosted by: [xuu](mailto:[email protected]), [nurtic-vibe](mailto:[email protected]), [siska](mailto:[email protected]), [toBee](mailto:[email protected]), [Mic92](mailto:[email protected]) \| Accessible via: [dn42](http://wiki.dn42), [tor](http://jsptropkiix3ki5u.onion), [i2p](http://beb6v2i4jevo72vvnx6segsk4zv3pu3prbwcfuta3bzrcv7boy2q.b32.i2p/)
...	...	\ No newline at end of file

...	...	@@ -2,43 +2,46 @@
2	2
3	3	[[_TOC_]]
4	4
5		-### Why are you using monotone for the registry? Why not Git?
	5	+### How do I connect to DN42 ?
6	6
7		-There is an important difference between the data model of monotone and Git: In Git branches are heads, while in monotone, branches are a list of heads. Or, to state it simpler and probably less correct: It is possible to sync merge conflicts in monotone. In Git, conflicts are part of the index and/or working tree, and thus can't be pushed/pulled.
	7	+We have a [page](/howto/Getting-started) for that !
8	8
9		-The DN42 registry is stored on multiple monotone servers which sync with each other. This is not possible in Git, because the Git servers don't know how to handle merge conflicts. In monotone, the servers just sync the conflict.
	9	+### What BGP daemon should I use?
10	10
	11	+This is really up to you: that's the magic of open protocols.
11	12
12		-### What about IPv6 in dn42?
	13	+Many users run Bird or FRRouting in a VPS, but there is a variety of BGP implementations in use across the network and some networks even run hardware routers or experimental software. DN42 is a great place to try out and get familiar with your implementation of choice in a live network.
13	14
14		-There are some ASes in dn42 that route IPv6 traffic. They generally use the "Unique Local Address" range (ULA, fd00::/8) defined by [RFC 4193](https://tools.ietf.org/html/rfc4193). A minor disadvantage of using ULAs is that you need to announce two prefixes in your LAN if you want to use stateless autoconfiguration and no NAT: The ULA and a globally routed prefix. Usually, this works fine, but it may cause issues with legacy clients which don't implement [RFC 6172](https://tools.ietf.org/html/rfc6172) correctly.
	15	+### Can I connect to DN42 from home through my ISP ?
15	16
16		-To get your own ULA range, simply pick a random prefix of the form fdXX:XXXX:XXXX/48 and enter it into the dn42 registry to make sure there are no collisions.
	17	+Sure. As long as you have a 24/7 connection, can configure VPN tunnels and run BGP then you can connect to DN42. Do let your peers know if you have a dynamic IP address and you may also want to consider preventing transit traffic through your network if you have a relatively slow connection.
17	18
18		-In theory, globally routable IPv6 networks could also be used inside dn42. However, this would complicate prefix filtering for everybody, and might lead to strange routing patterns, where packets are routed partially on dn42 and partially through the Internet. Most dn42 ASes filter such IPv6 prefixes, which means you'd have a hard time making them reachable in dn42.
	19	+Many users do use a virtual private server (VPS) for connecting to DN42. A VPS is a relatively cheap option that is always on and which (typically) provides a faster, more stable connection than your home. VPS have another advantage that if you mess something up, you won't break your home access to the internet.
19	20
20		-At the moment, it is safe to assume that everyone doing IPv6 routing accepts at least prefixes from fd00::/8 with prefix lengths between 48 and 64 bits (inclusive) if they are part of the registry.
	21	+### Does the registry use monotone or git ?
21	22
	23	+The DN42 registry used to be maintained in monotone, but was moved to git following resource and performance
	24	+issues. There may still be references back to monotone in some of the documentation, but the registry location is now:
22	25
23		-### Why are you using ASN in the 76100-76199 range?
	26	+https://git.dn42.us/dn42/registry
24	27
25		-Yes, we know that this is not private ASN space (rather, it is part of the reserved block 65552-131071, see [IANA](http://www.iana.org/assignments/as-numbers/as-numbers.xhtml)).
26	28
27		-We used to assign ASN in the 64600-64855 range, where you would get ASN 64600+X if you had 172.22.X.0/24. Since we are now assigning /25 by default, and we have extended the address range to include 172.23.0.0/16, this is legacy.
	29	+### What about IPv6 in dn42?
28	30
29		-Another issue with the private ASN range 64512-65534: other projects are also using it (for instance, Freifunk, Anonet, etc), which can lead to conflicts.
	31	+DN42 supports IPv6 and some users do run IPv6 only networks. DN42 uses the "Unique Local Address" range (ULA, fd00::/8) defined by [RFC 4193](https://tools.ietf.org/html/rfc4193).
30	32
31		-Fortunately, [RFC6996](http://tools.ietf.org/html/rfc6996) defines a new private ASN range: 4200000000-4294967294. Given the size of this range, there is little chance of running into a conflict.
	33	+Globally routable IPv6 prefixes are not supported in DN42; whilst in theory they could be announced, most networks will reject the prefixes and some networks will filter traffic to the ULA range only.
32	34
33		-We now encourage dn42 users to use the newly-allocated ranges in 4242420000-4242429999. See the [registry page](Services/Whois#AS-numbers) for details.
	35	+### Why are you using ASN in the 76100-76199 range?
34	36
	37	+DN42 now uses ASNs in the 4242420000-4242429999 range, but the 76100-76199 range was used historically, and there are still a very small number of networks using legacy ASNs that have not migrated.
35	38
36		-### What BGP daemon should I use?
	39	+Previously, DN42 has used a two other ASN ranges:
37	40
38		-This is really up to you: that's the magic of open protocols.
	41	+We used to assign ASN in the 64600-64855 range, where you would get ASN 64600+X if you had 172.22.X.0/24. Once the address range was extended to include additional blocks, this process was obsoleted. Another issue with the private ASN range 64512-65534 was that other projects are also using it (for instance, Freifunk, Anonet, etc), which can lead to conflicts.
39	42
40		-As of 2014, most people seem to use either Quagga or Bird (with a growing preference for Bird). You may also encounter users of OpenBGPd. Even more occasionally, people use hardware BGP routers in dn42, for instance [Extreme Networks](howto/bgp-on-extreme-summit1i) hardware.
	43	+Prior to using ASNs in the new private ASN range 4200000000-4294967294 ([RFC6996](http://tools.ietf.org/html/rfc6996)) Some ASNs were allocated from the [ASN reserved block](http://www.iana.org/assignments/as-numbers/as-numbers.xhtml) in the 76100-76199 range.
41	44
42	45	### Can I update the wiki?
43	46
44		-Yes, but only when connecting to this site via dn42 over SSL.
...	...	\ No newline at end of file
	0	+Yes, the wiki can be edited when browsing to [wiki.dn42](https://wiki.dn42).
...	...	\ No newline at end of file