Re: [atlas] Paris-traceroute variations
Hi all, Just a quick question. What is the real difference between a TCP paris-traceroutes and an UDP paris-traceroute ? How do the probes perform each of them? Thanks, Best regards, Roderick On 26.06.2014 13:13, Philip Homburg wrote:
Hi Juan,
On 2014/06/19 16:59 , Juan Antonio Cordero Fuertes wrote:
Not sure this is the right place to ask this... sorry if it is not.
I'm trying to configure Paris-traceroute measurements, and it is not clear for me what is the meaning of the /paris/ parameter. In https://atlas.ripe.net/docs/udm/ it is said that it corresponds, for values from 1 to 16, to "the number of variations to be used for a Paris traceroute <http://www.paris-traceroute.net/>". What is this? Does it correspond to the number of initial probes to be used by paris-traceroute? I am unable to figure it out from the RIPE Atlas docs... any indication would be appreciated.
Paris-traceroute tries to make sure that all packets of a traceroute take the same route through a load balancer. This in contrast to traditional traceroute where packets from different hops typically take different routes when load balancers are involved.
However, in the case of paris-traceroute it is still interesting to find out if there are multiple routes or not. For this reason, the traceroute measurement creates different variations that may take a different route.
Each interval, it will try one variation. So if you select 16 variations then it will take 16 intervals before you get back to the first one.
Philip
On 2014/07/31 11:14 , FANOU Roderick wrote:
Hi all, Just a quick question. What is the real difference between a TCP paris-traceroutes and an UDP paris-traceroute ? How do the probes perform each of them?
The Atlas traceroute can perform traceroute over ICMP, TCP, and UDP. The difference here is which protocol is used to send the probing packets. Beyond that, the 'paris' option tries to create packets in such a way that the computed flow id is stable during a run of traceroute. This can be done in different ways for ICMP, TCP, and UDP. Philip
participants (2)
-
FANOU Roderick
-
Philip Homburg