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 16:43:32 +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=HdqlMI JKbLc06wKjOsU/YZk5caiLzZKexjnwA2jTlHiM68TWgdrKtNbybRhhLu2Vtwb4m0 jS6eD03WOAC3m4grPO8Y33u/tlWjJBBeInGTOTj0GbP2MwadmYg01Ixh9YtGY/it OQQIQOzg7HcFo0T9dXzeZFNC/avlkMo0gd574=

On 05/11/2015 16:23, Brian Candler wrote:
bwctl: exec_line: ping6 -c 10 -i 1.000000 -s 1000 -m 255 -S 2001:db8:1:64::252 2001:db8:0:2::254
OK, I can replicate this at the command line. On the perfsonar 3.5 node:

$ bwping -t 255 -c <remote-OSX-node-running-bwctl> # works fine, but:

$ bwping -t 255 -s <remote-OSX-node-running-bwctl>
bwping: Using tool: ping
bwping: 21 seconds until test results available

SENDER START
ping6: setsockopt(IPV6_RECVPATHMTU): Operation not permitted
bwctl: local tool exited before expected with status=1

SENDER END


This seems to be another symptom of perfsonar changing the tests around, as I already saw for traceroute.

(1) What I had *configured* was a ping test on the perfsonar node, with the target as the OSX node.

(2) What I *expected* was simply for the perfsonar node to ping the OSX node. This was working in perfsonar 3.4.x

(3) What appears to be *happening now* is that perfsonar is using bwping to ask bwctld on the remote host to run a ping test *from* the remote node *back* to the perfsonar node.

This is problematic on several levels:

- I didn't want bwping to be used. "ping" tests in perfsonar are not very useful if they cannot be used to ping dumb hosts that are not running bwctl

In fact, the perfsonar 3.4 node I have is being used to ping some dumb routers; this will prevent me from upgrading that box to 3.5.

- The pings are now being originated from the OSX side; I expected the pings to originate from the perfsonar side

- OSX bwctld for ping is broken. As it turns out, "-m 255" is the correct way to specify TTL 255 on OSX, but there is some sort of socket permissions problem which prevents it working.

These problems would go away if perfsonar went back to its original approach of originating traceroute and ping from the perfsonar node, not from the remote node.


This still leaves the issue of why IPv4 pings aren't working, and I haven't got to the bottom of that yet.

Regards,

Brian.




Archive powered by MHonArc 2.6.16.

Top of Page