perfsonar-user - Re: [perfsonar-user] Perfsonar behind NAT
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Jason Zurawski <>
- To:
- Cc:
- Subject: Re: [perfsonar-user] Perfsonar behind NAT
- Date: Thu, 11 Dec 2014 13:07:37 -0500
Hello;
Unfortunately the perfSONAR tools (BWCTL, OWAMP) that would participate in a
regular testing fashion will not work with NAT. In most cases the tools need
to bind to a specific address as a part of their protocol operation.
There are ways to work around this on the command line, for example BWCTL can
function if one end of the connection has a non-natted address. There is an
option called —flip that will reverse the direction of the control protocol
to enable communication. OWAMP will not be able to work with a NAT due to
the way it is designed.
To address the last issue, we do not have an IRNC channel.
Thanks;
-jason
On Dec 11, 2014, at 11:01 AM,
wrote:
> Hi,
>
> I'm currently evaluating perfsonar with 1 central (DC) and several
> satellites
> sites (offices). Each of those offices are linked to the central site by
> IPsec
> tunnels but I'd also want to do measurements directly via Internet in
> parallel.
>
> So I NATed the central node and added the public hostname as a destination
> for
> the checks but the nodes seem confused as it's still the same central one.
>
> So I'm wondering if there is a way make it works, maybe have a 2nd interface
> dedicated to the NAT? Or any other way?
>
> Also is there an IRC channel for perfsonar somewhere?
>
> Thanks
- [perfsonar-user] Perfsonar behind NAT, arzhel, 12/11/2014
- Re: [perfsonar-user] Perfsonar behind NAT, Jason Zurawski, 12/11/2014
Archive powered by MHonArc 2.6.16.