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:08:36 +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:content-transfer-encoding; q=dns; s=sasl; b=Nj1FId oOLOK14M/sMYHkqRTXUsdi06qiyW49eXTB4ML8ec/dTYeE8NlvvADfT0pg/Rxi/J AjfJS/AFqmw9gT9/VvrNkF26szKATGmYDGlh27wR5rOmIHHoCPfdygMBTpD4GBCL gyr2iHn3pU1S99VfyFhCE1s1XFAA8cfJ3T5l8=
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 turns out it's because they were talking to Macs which have two different versions of traceroute, despite both running OSX 10.10.5:
Ignore that part. I was typing into a wrong window. Both Macs have:

$ ls -l /usr/sbin/traceroute*
-r-sr-xr-x 1 root wheel 33968 19 Sep 2014 /usr/sbin/traceroute
-r-sr-xr-x 1 root wheel 29648 19 Sep 2014 /usr/sbin/traceroute6

Further investigation required about the direction of traceroute tests which the perfsonar boxes were requesting.


Archive powered by MHonArc 2.6.16.

Top of Page