☰

Updated Route Beacon (markdown)

DN42 Wiki (BURBLE-MNT) committed 2022-04-06 16:56:08 +0000 commit f83a38cb109f99e312b74abf4604daa5f7c846a1

				services/Route-Beacon.md
			
          @@ -1,4 +1,4 @@

           There is a route beacon periodically advertising and withdrawing the prefixes 172.21.100.24/29 and fd40:e3b7:1d77:1234::/64. These are the only prefixes of as4242421933.

          -The schedule is the following: the prefixes are announced in every hour in between minutes 1-10, and withdrawn when the clock is outside of the above mentioned period.

          +The schedule is the following: the prefixes are announced in every even (cest) hour in between minutes 1-10, and withdrawn when the clock is outside of the above mentioned period.

           The main purpose of the whole experiment is to be able to spot the ghosting implementations.

           The current state could be monitored on the prometheus or nrpe endpoint at test.nop.dn42 or one can query the last recorded ghosting state by telnetting the same endpoint and issuing commands from the banner.

...	...	@@ -1,4 +1,4 @@
1	1	There is a route beacon periodically advertising and withdrawing the prefixes 172.21.100.24/29 and fd40:e3b7:1d77:1234::/64. These are the only prefixes of as4242421933.
2		-The schedule is the following: the prefixes are announced in every hour in between minutes 1-10, and withdrawn when the clock is outside of the above mentioned period.
	2	+The schedule is the following: the prefixes are announced in every even (cest) hour in between minutes 1-10, and withdrawn when the clock is outside of the above mentioned period.
3	3	The main purpose of the whole experiment is to be able to spot the ghosting implementations.
4	4	The current state could be monitored on the prometheus or nrpe endpoint at test.nop.dn42 or one can query the last recorded ghosting state by telnetting the same endpoint and issuing commands from the banner.