perfSONAR User Q&A and Other Discussion

[Ji-Sun Kim <>]

(Follow-up)

Since I need the iptables firewall after I talked with the IT person, I narrowed the ephemeral range (/proc/sys/net/ipv4/ip_local_port_range ) a bit and added the ephemeral range in the iptables.

Now NDT with -m option works well with the iptables firewall.

BTW, is still the --mrange option working? When I added the --mrange option, but my NDT instance is still in the single client mode.

Best,

Kim

On Sat, Aug 22, 2015 at 11:16 PM, Ji-Sun Kim <> wrote:

Hi Aaron,

Your kind responses gave me the clue of the issue!

I searched and found what caused the problem from the old posting.

https://lists.internet2.edu/sympa/arc/ndt-users/2005-08/msg00014.html

When using -m option, NDT server uses ephemeral ports for the client connections. However, if iptables rule is enabled and if the assigned port is not in the rule, then the connection is immediately failed.

I temporarily turned off the iptables rules and my NDT instance works well for multiple connections.

I may need to look into how to set up the firewall without using iptables.

Best,

Kim

On Sat, Aug 22, 2015 at 9:21 AM, Aaron Brown <> wrote:

Hi,

I apologize for the delay, I just got a chance to test it out. When I added the '-m' to my NDT instance, I was able to do multiple tests simultaneously using the websockets backend using Firefox.

Given the error message that you noted, I'm not sure why it attempted to connect to 34061. Do you have a firewall running? I wonder if it's doing the firewall test, and timing out for some reason. I can't fathom why that same issue wouldn't crop up in non-multitest mode though.

Cheers,

Aaron

On Fri, Aug 21, 2015 at 2:05 PM, Ji-Sun Kim <> wrote:

Hi,

I need to report my supervisor whether or not the current version of NDT/PerfSONAR can support the multiple client-requests simultaneously.

If there is anyone who is running the most recent version of NDT with PerfSONAR (pS-Performance Toolkit    3.4.2; NDT 3.7.0.2-1.el6), please help me on how to do it.

Best,

Kim

 

On Mon, Aug 17, 2015 at 12:34 PM, Ji-Sun Kim <> wrote:

I missed the error message below in my previous message, shown in the _javascript_ console when using -m option.

WebSocket connection to
'ws://domainname:34061/ndt_protocol' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT

(FYI, I used http://domainname:7123)

Best,

Kim

On Mon, Aug 17, 2015 at 9:48 AM, Ji-Sun Kim <> wrote:

Hi Aaron,

I used FireFox (40.0.2) with Firebug but there was no error message found at all.

Otherwise, please let me know which part I should specifically look at.

Instead I looked at the web100srv.log and the log messages are as follows (with -m option) when using two client requests:

Aug 17 12:36:41  'ipaddress' port 50401
Signal 17 received by process 31834
Aug 17 12:37:04   'ipaddress' port 50421
Signal 17 received by process 31834

Nothing is going further from there.

Any suggestion?

Thanks!

Kim

On Mon, Aug 17, 2015 at 6:01 AM, Aaron Brown <> wrote:

Hi,

Could you try running with the _javascript_ debug console open? The specifics of that will depend on the browser you're using.

Cheers,

Aaron

On Sunday, August 16, 2015, Ji-Sun Kim <> wrote:

Hi Aaron,

I am using only Websocket backend.

Best,

Kim

On Sun, Aug 16, 2015 at 5:17 PM, Aaron Brown <> wrote:

Hi,

Are you using the java or websocket backend?

Cheers,
Aaron

On Aug 13, 2015 3:32 PM, "Ji-Sun Kim" <> wrote:

Hi Andy,

Thank you for your follow-up message.

I attempted the -m option in the 'ndt' file but it didn't work.

The multiple connections worked but nothing happened further. None of clients started the test with ndt or failed but just waited forever. With the -m option, even a single client didn't start testing. I also attempted to use "--mrange port1:port2" that didn't work either.

I searched the mailing list archive. It seemed that "-m" was used to be working before but I am not sure if it still works...

FYI, here is the software version list that I am currently using.

Software Versions
pS-Performance Toolkit    3.4.2 (3.4.2-13.pSPS)
BWCTL    1.5.4-1.el6
OWAMP    3.4-10.el6
NDT    3.7.0.2-1.el6
NPAD    1.5.6-3.el6
esmond Measurement Archive    1.0-14.el6
perfSONAR-PS Regular Testing Daemon    3.4.2-5.pSPS
iperf3    3.0.11-1.el6

Please let me know if there is any other suggestion that I can try.

(I also posted the same question to the ndt-users mailing-list.)

Thanks!

Kim

On Thu, Aug 13, 2015 at 9:26 AM, Andrew Lake <> wrote:

Hi,

The original NDT developer just informed me that you can do this by adding the “-m” option to your ndt server command. Assuming this is on a toolkit host using the NDT RPM, you can update the existing WEB100SRV_OPTIONS variable to include -m in the file /etc/sysconfig/ndt. Run "/etc/init.d/ndt restart” after the change and you should be able to run multiple tests. 

Thanks,

Andy

On Thu, Aug 13, 2015 at 9:19 AM, Andrew Lake <> wrote:

Hi,

As far as I know there is not a way to change the behavior. This is by design so that tests do not interfere with each other. There is also an mailing list where there might be others that know some tricks of which I am unaware. 

Thanks,

Andy

On Wed, Aug 12, 2015 at 12:56 PM, Ji-Sun Kim <> wrote:

Hello,

I would like to make my NDT/PerfSONAR server handle multiple requests from Web (http) clients simultaneously. It seems that the default setting only allows a single request.

I appreciate if anyone can help on it.

Thanks!

Kim