services/Distributed-Wiki.md
... ...
@@ -188,7 +188,7 @@ server {
188 188
189 189
#### Announcing
190 190
191
-The prefix AS-PATH should show the announcement is originating from your AS. After peering ExaBGP to the nearest speaker(s), check if the prefix is routing properly inside your network. Try not to blackhole the passing traffic (e.g. no static routes to `172.23.0.80/28`). Test the whole thing by shutting down nginx/gollum and watch what happens.
191
+The prefix AS-PATH should show the announcement is originating from your AS. After peering ExaBGP to the nearest speaker(s), check if the prefix is routing properly inside your network. Try not to blackhole the passing traffic (e.g. no static routes to `172.23.0.80/32`). Test the whole thing by shutting down nginx/gollum and watch what happens.
192 192
193 193
#### Configuration
194 194
... ...
@@ -242,8 +242,7 @@ CURL=curl
242 242
## url's to check (all listed must be alive to send announce)
243 243
URL=("http://172.23.0.80" "https://172.23.0.80" "http://[fd42:d42:d42:80::1]" "https://[fd42:d42:d42:80::1]")
244 244
245
-## the anycast route (/28 due to prefix size limits)
246
-ROUTE='172.23.0.80/28'
245
+ROUTE='172.23.0.80/32'
247 246
## the anycast v6 route (/64 due to prefix size limits)
248 247
ROUTE6='fd42:d42:d42:80::/64'
249 248