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/[email protected]/
[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
Wed Feb 17 17:28:40 CET 2021
On 2021/02/16 19:39 , Randy Bush wrote: >> I think the answer very much depends on who you ask. > > with my researcher hat on, i am curious yellow. with a minor concern > for how much of the lab's resources it would consume. I just did a small experiment with the probe firmware. Allowing 240.0.0.0/4 and 0.0.0.0/8 is a two line change. I tested this on V3 and V4 probes and on CentOS 7. In all 3 cases, the linux kernel does support 240.0.0.0/4 and does not support 0.0.0.0/8. We are not going to releasing new firmware for V1 and V2 (except to address security issues). So this a relatively small change that can go out with a future firmware release. Currently the Atlas API also blocks these netblocks. I assume, but did not verify, that this will also be a small change. In short, supporting this request is going to take only a tiny bit of time to support. Philip
- 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 ]