0ff3b8919565eeda7c856826dfd237cdf10ed5f2
howto/Getting-started.md
... | ... | @@ -97,8 +97,49 @@ If you want to register an [IPv6 prefix](/FAQ#frequently-asked-questions_what-ab |
97 | 97 | |
98 | 98 | [Unique Local IPv6 Generator](http://unique-local-ipv6.com/) |
99 | 99 | |
100 | +example: inet6num/fd42:4992:6a6d::_48 |
|
101 | +``` |
|
102 | +inet6num: fd42:4992:6a6d:0000:0000:0000:0000:0000 - fd42:4992:6a6d:ffff:ffff:ffff:ffff:ffff |
|
103 | +netname: EVE-NETWORK |
|
104 | +descr: Network of eve |
|
105 | +country: DE |
|
106 | +admin-c: MIC92-DN42 |
|
107 | +tech-c: MIC92-DN42 |
|
108 | +mnt-by: MIC92-MNT |
|
109 | +nserver: ns1.evenet.dn42 |
|
110 | +nserver: ns2.evenet.dn42 |
|
111 | +status: ASSIGNED |
|
112 | +``` |
|
113 | + |
|
114 | +example: inetnum/172.23.75.0_24 |
|
115 | +``` |
|
116 | +inetnum: 172.23.75.0 - 172.23.75.255 |
|
117 | +netname: EVE-NETWORK |
|
118 | +admin-c: MIC92-DN42 |
|
119 | +tech-c: MIC92-DN42 |
|
120 | +mnt-by: MIC92-MNT |
|
121 | +nserver: ns1.evenet.dn42 |
|
122 | +nserver: ns2.evenet.dn42 |
|
123 | +status: ASSIGNED |
|
124 | +``` |
|
125 | + |
|
100 | 126 | If you plan to announce this network in dn42, which you probably want in most cases, you also need to create a `route` object for ipv4 and a `route6` object for ipv6. This information is used for ROA checks (route origin authorization). If you skip this step, your network gets probably filtered by some peers. |
101 | 127 | |
128 | +example: route6/fd42:4992:6a6d::_48 |
|
129 | +``` |
|
130 | +route6: fd42:4992:6a6d::/48 |
|
131 | +origin: AS4242420092 |
|
132 | +mnt-by: MIC92-MNT |
|
133 | +``` |
|
134 | + |
|
135 | +example route/172.23.75.0_24: |
|
136 | +``` |
|
137 | +route: 172.23.75.0/24 |
|
138 | +origin: AS4242420092 |
|
139 | +mnt-by: MIC92-MNT |
|
140 | +bgp-status: active |
|
141 | +``` |
|
142 | + |
|
102 | 143 | # Get some peers |
103 | 144 | |
104 | 145 | In dn42, there is no real distinction between peering and transit: in most cases, everybody serves as an upstream provider to all its peers. Note that if you have very slow connectivity to the Internet, you may want to avoid providing transit between your peers, which can be done by filtering or prepending your ASN. For the sake of sane routing, try to peer with people on the same continent to avoid inefficient routing, <50ms is a good rule of thumb. You can also look into Bird communities if you are using Bird to mark the latency for the [link](/howto/Bird-communities). |