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 12:06:17 CET 2021
On 2021/02/17 17:56 , Randy Bush wrote: >> 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. > > so, what experiment(s) do you think would be useful once some capable > probes deploy? Traceroute seems to be the only measurement that makes sense. I noticed that my first hop router sends an error ICMP, but I don't get anything beyond that. >> We are not going to releasing new firmware for V1 and V2 (except to >> address security issues). > > i can not get to my v1 probes during covid lockdown even if you shipped > replacements to me :( < snif > Yes, it is amazing that corona doesn't seem to have much in the number of probes that are connected. > will you upgrade soft probes? or send instructions? 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). 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 ]