Skip to Content.
Sympa Menu

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

Subject: perfSONAR User Q&A and Other Discussion

List archive

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


Chronological Thread 
    < Chronological >      < Thread >
  • From: Ignacio Peluaga Lozada <>
  • To: "" <>
  • Subject: [perfsonar-user] Latency task with source and target behind NAT
  • Date: Fri, 13 Nov 2020 15:05:00 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 188.184.36.46) smtp.rcpttodomain=internet2.edu smtp.mailfrom=cern.ch; dmarc=bestguesspass action=none header.from=cern.ch; dkim=none (message not signed); arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1MAXVWDAMZjnhaCzp2C4iMGMeZE6pT2eAMIgYx3myx4=; b=ba4lHeu06We7Cw+zTctkdix6UN2t5Z+gWQTsyAn1AB0IfMtMjs05tsED27A+ChKDjydpX32vWUjtOl0vGwnWS7+1bSbW5C6iUm2+SuUT4R9PgrKRWzo5IkKYigxEfCkVdsWUNLLDMc/79unGGNG7EF745st0XmlR9pUXGa+n1Of278zKnDiFzzmikXSJ3KaEBXU/83uaNaiQ7wW+K+XLhIgkVS525Vwk6MhDqIAbtz31r25axUjVauWQDKwYCVCYPWfKdyO1T/41zTnx1AjTgqEBqokN2XE0fzWJ5oOKyPyf+BwdWKA82CX9cQxljPi0yWCk/eo5y4kUs1Bh5pMGMw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gwSfH0AJS26BOZCayqtUWDxuG5g1+AuSN99Hcb0W/xfWCLDyExupKtYxRG6DO4S3lWHDlrDyv0pDlhutTJUGn3CKGCpbwCxmkVqwLB7gXCRrfCN6Ovm5VfBYRRdkT3eAS5LTf64YHYMv/JOj7VA2+MFzCaShMjCV3H4JG4J3KaIqm6KL5b3Gf8iH599PcMvH5V41FIRform83MghH3SBiBIzl8xYApqIyet6lz8qryzeqZS7QoNVq62OjZoM/3ZOO1IzQ+uMr9yw26fWqj01iiAWqNuGbq6pJYmALmsc2ZdhZPSUaUzTWhKg1G3qYHScTTRtymF8IIaUjCcETyY4nA==
Hello,

our goal is to be able to run tests between two VMs both behind NAT.

Our scenario is:

-2 VMs running on different public clouds. Both of them have public IPs (NAT).
-On each VM, there is a perfSONAR testpoint Docker container running.
-The containers are run using: docker run -d --net=host
perfsonar/testpoint:4.2.4

We are able to run between these two nodes tasks such as rtt, trace (with
--tool tracepath) and throughput, however we didn't manage to get the latency
task to work.
We can however run from those two nodes latency tasks to other perfSONAR
nodes (note this example uses directly twping but will be available for
pscheduler too: https://github.com/perfsonar/pscheduler/issues/1082 thanks
for that!):

twping -Z psb01-gva.cern.ch

When we try that from one container to the other, we get:

twping: FILE=owping.c, LINE=1757, Unable to open control connection
to 80.158.55.226.

With that being said, let me please ask, is there any way to achieve that?
Maybe there's some configuration we are missing when deploying the containers
or prior to that?

Thanks in advance to all.

Regards,
Ignacio



Archive powered by MHonArc 2.6.19.

Top of Page