71249ccd9c7cf03beadf2bcf78051dcd735b0281
howto/Getting-started.md
| ... | ... | @@ -38,10 +38,11 @@ Create a `mntner` object in `data/mntner/` named `<FOO>-MNT`. It will be used to |
| 38 | 38 | |
| 39 | 39 | Example: data/mntner/EXAMPLE-MNT |
| 40 | 40 | ``` |
| 41 | -mntner: EXAMPLE-MNT |
|
| 42 | -admin-c: EXAMPLE-DN42 |
|
| 43 | -tech-c: EXAMPLE-DN42 |
|
| 44 | -mnt-by: EXAMPLE-MNT |
|
| 41 | +mntner: EXAMPLE-MNT |
|
| 42 | +admin-c: EXAMPLE-DN42 |
|
| 43 | +tech-c: EXAMPLE-DN42 |
|
| 44 | +mnt-by: EXAMPLE-MNT |
|
| 45 | +source: DN42 |
|
| 45 | 46 | ``` |
| 46 | 47 | |
| 47 | 48 | ### Create person objects |
| ... | ... | @@ -59,10 +60,11 @@ Create a `person` object in `data/person/` for **yourself** (not your organisat |
| 59 | 60 | |
| 60 | 61 | Example: data/mntner/EXAMPLE-DN42 |
| 61 | 62 | ``` |
| 62 | -person: John Doe |
|
| 63 | -contact: [email protected] |
|
| 64 | -nic-hdl: EXAMPLE-DN42 |
|
| 65 | -mnt-by: EXAMPLE-MNT |
|
| 63 | +person: John Doe |
|
| 64 | +contact: [email protected] |
|
| 65 | +nic-hdl: EXAMPLE-DN42 |
|
| 66 | +mnt-by: EXAMPLE-MNT |
|
| 67 | +source: DN42 |
|
| 66 | 68 | ``` |
| 67 | 69 | |
| 68 | 70 | Organisations are not required if you are joining dn42 as a single user. If you intend to register resources for an organisation (e.g. your hackerspace), you must also create an `organisation` object for your organisation: |
| ... | ... | @@ -76,11 +78,12 @@ Organisations are not required if you are joining dn42 as a single user. If you |
| 76 | 78 | |
| 77 | 79 | Example: data/organisation/ORG-EXAMPLE |
| 78 | 80 | ``` |
| 79 | -organisation: ORG-EXAMPLE |
|
| 80 | -org-name: Example Organisation |
|
| 81 | -admin-c: EXAMPLE-DN42 |
|
| 82 | -tech-c: EXAMPLE-DN42 |
|
| 83 | -mnt-by: EXAMPLE-MNT |
|
| 81 | +organisation: ORG-EXAMPLE |
|
| 82 | +org-name: Example Organisation |
|
| 83 | +admin-c: EXAMPLE-DN42 |
|
| 84 | +tech-c: EXAMPLE-DN42 |
|
| 85 | +mnt-by: EXAMPLE-MNT |
|
| 86 | +source: DN42 |
|
| 84 | 87 | ``` |
| 85 | 88 | |
| 86 | 89 | ### Guidelines for future objects |
| ... | ... | @@ -107,11 +110,12 @@ If unsure, ask on the mailing list or IRC. |
| 107 | 110 | |
| 108 | 111 | Example: data/aut-num/AS4242423999 |
| 109 | 112 | ``` |
| 110 | -aut-num: AS4242423999 |
|
| 111 | -as-name: AS for EXAMPLE Network |
|
| 112 | -admin-c: EXAMPLE-DN42 |
|
| 113 | -tech-c: EXAMPLE-DN42 |
|
| 114 | -mnt-by: EXAMPLE-MNT |
|
| 113 | +aut-num: AS4242423999 |
|
| 114 | +as-name: AS for EXAMPLE Network |
|
| 115 | +admin-c: EXAMPLE-DN42 |
|
| 116 | +tech-c: EXAMPLE-DN42 |
|
| 117 | +mnt-by: EXAMPLE-MNT |
|
| 118 | +source: DN42 |
|
| 115 | 119 | ``` |
| 116 | 120 | |
| 117 | 121 | ### Register a network prefix |
| ... | ... | @@ -124,17 +128,18 @@ To register an [IPv6 prefix](/FAQ#frequently-asked-questions_what-about-ipv6-in- |
| 124 | 128 | |
| 125 | 129 | example: data/inet6num/fd42:4992:6a6d::_48 |
| 126 | 130 | ``` |
| 127 | -inet6num: fd42:4992:6a6d:0000:0000:0000:0000:0000 - fd42:4992:6a6d:ffff:ffff:ffff:ffff:ffff |
|
| 128 | -cidr: fd42:4992:6a6d::/48 |
|
| 129 | -netname: EVE-NETWORK |
|
| 130 | -descr: Network of eve |
|
| 131 | -country: DE |
|
| 132 | -admin-c: MIC92-DN42 |
|
| 133 | -tech-c: MIC92-DN42 |
|
| 134 | -mnt-by: MIC92-MNT |
|
| 135 | -nserver: ns1.evenet.dn42 |
|
| 136 | -nserver: ns2.evenet.dn42 |
|
| 137 | -status: ASSIGNED |
|
| 131 | +inet6num: fd42:4992:6a6d:0000:0000:0000:0000:0000 - fd42:4992:6a6d:ffff:ffff:ffff:ffff:ffff |
|
| 132 | +cidr: fd42:4992:6a6d::/48 |
|
| 133 | +netname: EVE-NETWORK |
|
| 134 | +descr: Network of eve |
|
| 135 | +country: DE |
|
| 136 | +admin-c: MIC92-DN42 |
|
| 137 | +tech-c: MIC92-DN42 |
|
| 138 | +mnt-by: MIC92-MNT |
|
| 139 | +nserver: ns1.evenet.dn42 |
|
| 140 | +nserver: ns2.evenet.dn42 |
|
| 141 | +status: ASSIGNED |
|
| 142 | +source: DN42 |
|
| 138 | 143 | ``` |
| 139 | 144 | |
| 140 | 145 | #### IPv4 (Legacy) |
| ... | ... | @@ -166,15 +171,16 @@ To register for example 172.20.150.0/27, you need to fill in 172.20.150.0-172.20 |
| 166 | 171 | |
| 167 | 172 | example: data/inetnum/172.23.75.0_24 |
| 168 | 173 | ``` |
| 169 | -inetnum: 172.23.75.0 - 172.23.75.255 |
|
| 170 | -cidr: 172.23.75.0/24 |
|
| 171 | -netname: EVE-NETWORK |
|
| 172 | -admin-c: MIC92-DN42 |
|
| 173 | -tech-c: MIC92-DN42 |
|
| 174 | -mnt-by: MIC92-MNT |
|
| 175 | -nserver: ns1.evenet.dn42 |
|
| 176 | -nserver: ns2.evenet.dn42 |
|
| 177 | -status: ASSIGNED |
|
| 174 | +inetnum: 172.23.75.0 - 172.23.75.255 |
|
| 175 | +cidr: 172.23.75.0/24 |
|
| 176 | +netname: EVE-NETWORK |
|
| 177 | +admin-c: MIC92-DN42 |
|
| 178 | +tech-c: MIC92-DN42 |
|
| 179 | +mnt-by: MIC92-MNT |
|
| 180 | +nserver: ns1.evenet.dn42 |
|
| 181 | +nserver: ns2.evenet.dn42 |
|
| 182 | +status: ASSIGNED |
|
| 183 | +source: DN42 |
|
| 178 | 184 | ``` |
| 179 | 185 | |
| 180 | 186 | #### Create route objects |
| ... | ... | @@ -183,16 +189,18 @@ If you plan to announce your prefixes in dn42, which you probably want in most c |
| 183 | 189 | |
| 184 | 190 | example: data/route6/fd42:4992:6a6d::_48 |
| 185 | 191 | ``` |
| 186 | -route6: fd42:4992:6a6d::/48 |
|
| 187 | -origin: AS4242420092 |
|
| 188 | -mnt-by: MIC92-MNT |
|
| 192 | +route6: fd42:4992:6a6d::/48 |
|
| 193 | +origin: AS4242420092 |
|
| 194 | +mnt-by: MIC92-MNT |
|
| 195 | +source: DN42 |
|
| 189 | 196 | ``` |
| 190 | 197 | |
| 191 | 198 | example data/route/172.23.75.0_24: |
| 192 | 199 | ``` |
| 193 | -route: 172.23.75.0/24 |
|
| 194 | -origin: AS4242420092 |
|
| 195 | -mnt-by: MIC92-MNT |
|
| 200 | +route: 172.23.75.0/24 |
|
| 201 | +origin: AS4242420092 |
|
| 202 | +mnt-by: MIC92-MNT |
|
| 203 | +source: DN42 |
|
| 196 | 204 | ``` |
| 197 | 205 | |
| 198 | 206 | # Get some peers |