Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Perfsonar & IPv6 behavior

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Perfsonar & IPv6 behavior


Chronological Thread 
  • From: Mark Feit <>
  • To: Garret Peirce <>, "" <>, "" <>
  • Subject: Re: [perfsonar-user] Perfsonar & IPv6 behavior
  • Date: Wed, 30 Oct 2019 14:54:20 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Yp+RYMdWfa/z6Msq+OqH6amENhvC52KO38KQWkuX/oc=; b=erDkOuIJIStDSHwmd4tNSLgNB0p3XrgRc5W2NPr8mTEa4KNSb8Oi8nEqSltD8QLOh2ef3tTKc4hxDXO1oXDhbITXMIY3UDb3QWKhDZu+60RDHPrakpaaqM7s+rszpsDSZf5bQUMVix4pSWstCbX5H164Rjt6XpgFbRy91WVYZ7J16hnjTvH7qpnsL17dvN/OAu0htgFRFG7UimgMqEBgIMXHI+c38xsR7EH8f7yRNNRg6vjAkcHw15tFfjUXXvj02UDE0Oz2SefEo+jponzvv1WWOXguTlyWY6mXDm46ImFQKSB41bKnClavjtHAOfwA4uyom42AKHZvLaBr3CNMGg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XbTYVYiTpV54hASgllG72tVuyAupBDVrHXLrLG3WjIRZkYNGd5axENkJI/0zPO95xyqJKzaE3ySNLOMUx2pHcTtj5WpabMgCKgAxgepQjhAIaq2LGm4vSzatJ8h9/9iIGEi1EiJfLIrRKNfzeczskm3hU8ji86VVjMPO1mT8oAby+zNHQGzg6C3R99BJIcW2MqFDTZF4HlorriJYt76tO7OkLsrmAvyaIrb21pfonAblKAtGV369ldcZdZxnJ3kYJoUX6HLZ4CI06G6aSNE5uHnzErHD1TEDqN4kj2Hy0twlEFz5czrBkEsDLKGaHKAmknn+QasvrLUM36nEMZFWMA==

Garret Peirce writes:

 

Participating in a group of nodes sharing a test JSON file, including the option is a bit painful as I'll have to edit the file for v6 only use after any changes - which I've yet to get back to try.  Once seems painful enough when there seems to be an easier solution, i.e. having perfsonar follow RFC6724 for address selection.  Perhaps there are reasons to prefer manual/fixed selection, so manual options should probably remain.  We're later than many to the game, so I was surprised to find this little chestnut, but sounds like we'll see a PS patch to improve its current behavior.

 

Manual won’t go away because a FQDN with A and AAAA records is ambiguous and there’d be no way to force one or the other.  I recommend using it because using a FQDN and letting the tool pick the protocol would conceal a failure by DNS to return a AAAA record by silently failing over to IPv4.

 

That said, the software should follow the RFC in the absence of a directive, so we will be going through all of the tool plugins to make sure they behave properly.  Most of the tool plugins call a library function that normalizes and resolves all of that; ping predates that and was never brought up to date.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page