howto/Getting-Started.md
... ...
@@ -32,6 +32,7 @@ The registry includes a number of scripts to help check your request:
32 32
- `check-my-stuff <FOO>-MNT`: validates your objects against the registry schema
33 33
- `check-pol origin/master <FOO>-MNT`: checks for policy violations
34 34
- `squash-my-commits`: automatically update and squash your local commits
35
+ - `sign-my-commit`: sign your commit using a pgp key or standard SSH signing
35 36
36 37
The registry maintainers run the checking scripts against each request, so please run these yourself first to check for simple errors.
37 38
... ...
@@ -141,7 +142,7 @@ Your AS number can be chosen arbitrarily in the dn42 ASN space, see the [as-bloc
141 142
142 143
**You should allocate your AS number in the 4242420000-4242423999 range**
143 144
144
-For a list of currently assigned AS numbers browse the registry data/aut-num/ directory or [online](https://explorer.burble.com/#/aut-num/).
145
+[dn42regsrv](https://explorer.burble.com/free#/asn) includes a page for finding free ASN. For a list of currently assigned AS numbers browse the registry data/aut-num/ directory or [online](https://explorer.burble.com/#/aut-num/).
145 146
146 147
If you intend to use an ASN outside of the native dn42 ranges, please check that it doesn't clash with the [Freifunk AS-Numbers] (http://wiki.freifunk.net/AS-Nummern) or other networks (ChaosVPN, etc).
147 148
... ...
@@ -152,7 +153,7 @@ If unsure, ask on the mailing list or IRC.
152 153
Example: data/aut-num/AS4242423999
153 154
```
154 155
aut-num: AS4242423999
155
-as-name: AS for FOO Network
156
+as-name: AS-FOO-DN42
156 157
admin-c: FOO-DN42
157 158
tech-c: FOO-DN42
158 159
mnt-by: FOO-MNT
... ...
@@ -168,6 +169,7 @@ To register an IPv6 prefix, you create an `inet6num` object. dn42 uses the fd00:
168 169
dn42 is interconnected with other networks, like icvpn, which also use the same ULA range so a registration in the dn42 registry can't prevent IPv6 conflicts. A fully random prefix (see [RFC4193](https://tools.ietf.org/html/rfc4193)) is recommended; finding a conflict and needing to renumber your network is no fun.
169 170
170 171
A few websites can generate random ULA prefixes for you:
172
+* [dn42regsrv](https://explorer.burble.com/free#/6)
171 173
* [SimpleDNS](https://simpledns.com/private-ipv6)
172 174
* [Ultratools](https://www.ultratools.com/tools/rangeGenerator)
173 175
... ...
@@ -193,7 +195,8 @@ If you also want to register an IPv4 network prefix, simply create an `inetnum`
193 195
194 196
You may choose your network prefix in one of the currently open netblocks. You can get a list of unassigned subnets on the following site, please mind the allocation guideline below.
195 197
196
- * [Open Netblocks](https://dn42.us/peers/free)
198
+* [Free blocks in dn42regsrv](https://explorer.burble.com/free#/4)
199
+* [Open Netblocks](https://dn42.us/peers/free)
197 200
198 201
Check the registry (data/inetnum) to make sure no-one else has allocated the same prefix. There are some IP ranges that are not open for assignments or are reserved for specific uses, so you should also check that the parent block has an 'open' policy. A quick and simple way to see the block policies is to run `grep "^policy" data/inetnum/*`.
199 202