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] Timeout on Ping Measurements
- Previous message (by thread): [atlas] Timeout on Ping Measurements
- Next message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Jul 15 16:13:23 CEST 2013
On 2013/07/14 19:35 , Rusty Dekema wrote: > > What is the default timeout on ICMPv4 user-defined measurements made > on RIPE Atlas? I am guessing something like 1.2 s based on > observations, but I'd like to know definitively. It should be 1 second. > Also, is it possible to increase the timeout? One of the targets I > have been measuring often takes a very long time to respond (due to > congestion or link-layer retries) and I would like to have a high (5 > second, perhaps) timeout on these pings. I haven't noticed an option > to set this when setting up the measurement, but it's very possible > I've overlooked something. At the moment there is no option to change the ping timeout. Traceroute does have that option. Philip
- Previous message (by thread): [atlas] Timeout on Ping Measurements
- Next message (by thread): [atlas] [UDM] What value to give to 'requested' when 'type' = 'msm'?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]