This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Previous message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Next message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Thu Feb 18 14:19:03 CET 2021
On 2021/02/18 14:13 , Chriztoffer Hansen wrote: > On Thu, 18 Feb 2021 at 12:06, Philip Homburg wrote: >> For a binary install of the CentOS RPM it should be automatic. For >> debian based, it is a matter of compiling a new .deb and upgrading >> (manually). > > An idea for a system-tag in the RIPE Atlas system? > > I.e. based on the (client) atlas probe software revision. Restrict > which probes/anchers would be permitted/allowed to run tests for IP's > in e.g. 240/4 space... That is part of the API backend. When probes are selected for a measurement, only those probes are selected that have a high enough firmware version. Though I have to admit, that will make this feature slightly more complex than I thought.
- Previous message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
- Next message (by thread): [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]