perfSONAR User Q&A and Other Discussion

[Jason Zurawski <>]

Greetings Daniel;

OWAMP will never work in a NAT'ed situation due to the way the protocol is constructed - the tool must be able to bind to the public IP on both sides. 

BWCTL can work provided that one end of the test is non-NAT'ed.  There is an option called 'flip' (see the man page) that allows the direction of the control channel to be reversed (e.g. public IP to NAT'ed IP) to allow the test to complete. 

There is some guidance on this page regarding what you can do to your regular testing setup:

http://docs.perfsonar.net/config_regular_testing.html

In particular pay attention to he 'local_firewall directive'.  If you enable this, it should allow the control channel to be always flipped on your NAT'ed host. 

Thanks;

-jason

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