perfSONAR User Q&A and Other Discussion

[Alex Hsia <>]

There shouldn't be any firewall blocking access to simplestream and the host is using the default perfSONAR default host level firewall rules, i.e.:

alex@nettest:~$ sudo iptables -L

...

ACCEPT     tcp  --  anywhere             anywhere             tcp dpts:5890:5900 ctstate NEW

Here's some output from tcpdump on nettest that shows the TCP syn getting to the host and the TCP reset getting sent.

09:14:31.499059 IP sdmz-perfsonar-40g.boulder.noaa.gov.33756 > nettest.boulder.noaa.gov.5893: Flags [S], seq 2011708581, win 35840, options [mss 8960,sackOK,TS val 775476829 ecr 0,nop,wscale 14], length 0
09:14:31.499139 IP nettest.boulder.noaa.gov.5893 > sdmz-perfsonar-40g.boulder.noaa.gov.33756: Flags [R.], seq 0, ack 2011708582, win 0, length 0

Alex Hsia ==============================================================
NOAA/OAR                                            Phone: (303)497-6351
Mailstop R/ESRL                                    GVoice: (303)536-5430
325 Broadway                                  e-mail:
Boulder, CO  80305                                   PGP keyid: 8A482A90
========================================================================

On Tue, May 28, 2019 at 7:31 AM Mark Feit <> wrote:

Alex Hsia writes:

 

  Simple stream test.... 12 seconds.... Failed.

Task failed to run properly.

…

Diagnostics from localhost:

  Try 1 failed: Failed to connect: [Errno 111] Connection refused

  …

 

I get the same failure from here.  The diagnostics from the far (nettest.boulder.noaa.gov) end say everything was good, so I suspect the firewall there is rejecting connections to the ports used for the simplestream test (see https://docs.perfsonar.net/manage_security.html).  Throughput to that host works fine.

 

--Mark