Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Latency task with source and target behind NAT

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Latency task with source and target behind NAT


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Ignacio Peluaga Lozada <>, "" <>
  • Subject: Re: [perfsonar-user] Latency task with source and target behind NAT
  • Date: Tue, 17 Nov 2020 19:21:15 +0000

Ignacio Peluaga Lozada writes:


Once again I have two VMs, on each there's a perfSONAR Docker container running.
Source VM is behind nat but target isn't, it has an interface with a public IP, 89.145.161.126.

So my question is, why can't I run twping to it? I tried the following (for all the possible combinations 4.2.4-latest for source and target):

        twping -Z 89.145.161.126
        twping: FILE=owping.c, LINE=1757, Unable to open control connection to 89.145.161.126.



The control part of that is just a regular TCP connection, so it’s probably a firewall or ACL problem.  Can you do a successful “pscheduler troubleshoot” between the two hosts?

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page