[atlas] Flow-id of built-in traceroute measurement
- Previous message (by thread): [atlas] Research using RIPE Atlas probes: How Pingable are the Pingables?
- Next message (by thread): [atlas] Flow-id of built-in traceroute measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wenqin SHAO
wenqin.shao at telecom-paristech.fr
Tue Apr 5 20:53:59 CEST 2016
Dear list, I have some questions concerning the flow-id of built-in traceroute measurements and are seeking for your help. As many of you may have already noticed, the flow-id of the built-in traceroute measurement periodically varies form 0 to 15, in a circular manner. With this behaviour, it is supposed to reveal the diversity of underlying IP paths. In the case that there are more than 16 unique IP paths between a source and destination pair, could this scheme reveal all of these IP paths? If it can, which leads to more than one IP paths per flow-id? Is it normal, from a load balancer point of view? If it can not, then why not a wider range of flow-id (more nuances in header hash results), say [0, 63]? Is it related to common realisation of load balancer? Many thanks in advance. Best regards, Wenqin ==== Wenqin SHAO PhD Candidate Telecom ParisTech
- Previous message (by thread): [atlas] Research using RIPE Atlas probes: How Pingable are the Pingables?
- Next message (by thread): [atlas] Flow-id of built-in traceroute measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]