perfsonar-user - Re: [perfsonar-user] Perfsonar ports - tracepath blocked

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Perfsonar ports - tracepath blocked

From: Brian Candler <>
To: Andrew Lake <>, "" <>
Subject: Re: [perfsonar-user] Perfsonar ports - tracepath blocked
Date: Tue, 16 Feb 2016 20:18:07 +0000
Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type; q=dns; s=sasl; b=vQLQA3AGzUbC5ihpiPMtwbZIFoS5CUlj QlRsPA6VFf0UionXBapkmJrLyLe46YYP3+7+/PV9DvH5lY02fAPMF7uPrYv7p+QP wF+9ZqTMP2DY/yctQNGlK4iaFNR+q0Ay+CvNARKtJ9LDK4UMmeMoRiFpGvXBtNMs vQBFEWUu698=

On 16/02/2016 20:15, Andrew Lake wrote:

Ugh sadly you are right that it doesn’t appear to be installing the reject. Looks like maybe a bug that was introduced for clean 3.5 installs. Expect a fix to be pushed to yum in the next 24 hours.

That makes sense. The older box was originally installed as 3.4 and upgraded itself, whilst the newer boxes were clean 3.5.

Will I still need to run
/opt/perfsonar_ps/toolkit/scripts/configure_firewall install
after the package has updated, or will the package itself take care of that?

Regards,

Brian.

RE: [perfsonar-user] Perfsonar ports - tracepath blocked, (continued)

List archive

Re: [perfsonar-user] Perfsonar ports - tracepath blocked