perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

We don’t officially support being behind a NAT so that’s not entirely unexpected.There are a few things you can try though. For the throughput tests, you might want to check out the —flip option the BWCTL command has which essentially make the reverse TCP test a download initiated by the local side, which should poke through your NAT properly. In /etc/perfsonar/regulartesting.conf this corresponds to the local_firewall option (http://docs.perfsonar.net/config_regular_testing.html#local-firewall-directive). On the OWAMP side, if you are seeing 100% loss in the reverse direction, that actually means the control connection is being established which is a good sign. You might want to verify you have UDP ports 8760-9960 mapped through in your NAT. 

Hope that helps,

Andy

On September 8, 2016 at 8:51:27 AM, Daniel Manzo () wrote:

Hi all,

 

My current perfSONAR setup is an HP server with 8 GB of RAM and an OS of RHEL 6.8. I installed using the CentOS bundle method with perfsonar-toolkit. My perfSONAR server is behind a firewall, but incoming ports are opened as long as my server is the one initiating testing. I have been able to successfully test outbound ping and throughput, but the reverse ping and throughput are not being reported. I have had 100% loss on latency tests as well. After running WireShark (packet sniffer), we have found that packets are being sent out successfully, but no packets are being reported as incoming at all. The server does use NAT (1:1) for its IP (public is 4.16.187.143). Any and all help is appreciated.

 

Thanks,

 

Dan Manzo