☰

Updated Anycast Wiki (markdown)

Anonymous committed 2015-03-30 12:17:06 +0200 commit 22d5a1c59d223abababfa7219382f9c5d04dd999

				internal/Anycast-Wiki.md
			
          @@ -235,6 +235,6 @@ exit 0

           ### Announcing:

          -The prefix AS-PATH should appear 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.

          +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.

          \ No newline at end of file

...	...	@@ -235,6 +235,6 @@ exit 0
235	235
236	236	### Announcing:
237	237
238		-The prefix AS-PATH should appear 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.
	238	+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.
239	239
240	240
...	...	\ No newline at end of file