Skip to Content.
Sympa Menu

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


Chronological Thread 
  • From: Brian Candler <>
  • To: "Garnizov, Ivan (RRZE)" <>, "" <>
  • Subject: Re: [perfsonar-user] Perfsonar ports - tracepath blocked
  • Date: Tue, 16 Feb 2016 12:49:11 +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:content-transfer-encoding; q=dns; s=sasl; b=LtGMeS yof8c5D1BxbQBsAvYucqYv0BNXiKIkn35t2BDtdPvQiYSIsUTqhz5RLT6q8p6UEN zhRTmXct76CQIaqdiu8VQzEeZS88ZN093rY0RIla1FNGxHjhoqhVPib4BU17OqNg bk28DATJKg0wvbYto/UmBmwlVKKN0Aj5uVjZk=

On 16/02/2016 12:44, Garnizov, Ivan (RRZE) wrote:
I believe there is something strange going on there.
I would not expect to have a tracepath daemon listening on any port.
There is no daemon which is "listening" on this port.

perfsonar is scheduling periodic runs of tracepath. When it runs, it creates a socket and binds to an ephemeral port in order to send packets. When it has finished, it terminates.

This is just how sockets work.

I would not expect to have a tracepath daemon at all!
There is no tracepath daemon, only the perfsonar scheduler which periodically runs tracepath.

Please share how do you come to this conclusion/inquiry: " tracepath only cares
about the intermediate hops and not the final destination"
perfsonar's own iptables rules do not permit tracepath packets in the port range I observed.

Therefore, either this is an oversight, or the perfsonar developers don't care about whether tracepath can reach the final hop or not.

Regards,

Brian.




Archive powered by MHonArc 2.6.16.

Top of Page