Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Re: Various breakages after 3.5 upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Re: Various breakages after 3.5 upgrade


Chronological Thread 
  • From: Brian Candler <>
  • To:
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Re: Various breakages after 3.5 upgrade
  • Date: Thu, 5 Nov 2015 15:42:44 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:cc:from:message-id:date:mime-version:in-reply-to :content-type; q=dns; s=sasl; b=oCiZZANXW1RixdgUFRVC7iLOHwxM10LI c/qh42whQ6K1IOUoS9gSWNQcdTWWz1X8xwnGqb9t3WjOitM5zlILLQh9NORc9TOj hcsdSzePt96hTuTHisKTlpIERLkO7Fo3y7lbtRuJrr99MY1xFT+IDM8XMRSrm0l6 JfXI1DgyoBg=

On 05/11/2015 15:05, Brian Candler wrote:
This then begs the question: why the difference between the perfsonar 3.4 and perfsonar 3.5 boxes?
It seems that perfsonar 3.5 records traceroute from (remote host) to (local host), while perfsonar 3.4 records traceroute from (local host) to (remote host)

At least, that's what I see when I go to the psTracerouteViewer page on those two nodes.

I don't know if that's an intentional change in behaviour between 3.4 and 3.5, or whether it's one of those things where perfsonar is non-deterministic as to what is "source" and what is "destination".

However, looking on the 3.5 box I can scan the measurement archive from before it upgraded to 3.4:



If I do this, I see there is traceroute information for (perfsonar node) -> (remote Mac) only up until Wed Sep 30 00:56:26 2015, which I think is when the upgrade took place.

There is IPv4 traceroute information for (remote Mac) -> (perfsonar node) starting Wed Sep 30 01:06:27 2015

And there is IPv6 traceroute information for (remote Mac) -> (perfsonar node) from when I fixed the traceroute6 parsing just now.

So it does look to me like perfsonar has changed which way it runs traceroutes.

Regards,

Brian.




Archive powered by MHonArc 2.6.16.

Top of Page