perfSONAR User Q&A and Other Discussion

[Miki <>]

Thanks for the answer Sowmya, 

Project is still not finished (it's a side project, so we are not in hurry ), but i will write what i have done. Maybe it will be helpful for someone in the future :) 

We haven't found what problem exactly is, "$telnet $test_host 861" was working, public address was acquired, but for owping i've been getting  "Unable to read from socket." error.  From the start, owampd was initialized with some custom test port range, and later it was set back to defaults, but problem remained. 

Then i have tried $owping -f and $owping -t (one way test to and one way test from test host) and then i got some results. I've noticed that ports that were used on the server were not in test range (owping statistics from [test_host]:53205 to [my_address]:8944 ), 53205 is not in range (8760-9960). That is most likely to cause the problem.

Investigation stopped there, because owping with parameters is also good for us. 

About RPi, from manual i know that i will need external clock source for better results. That is next thing to do. 

Best regards, 

Miki

2016-01-05 2:16 GMT+01:00 Sowmya Balasubramanian <>:

Hi Miki,

Try syncing the NTP to a clock source and running the test again.

I had some issues in the past, with owamp and bwctl running on Raspberry Pis that had NTP running, but not synced correctly to the clock source.

Sowmya

On Thu, Dec 24, 2015 at 5:35 AM, Miki <> wrote:

I have checked everything you have written, still not working.

But, i have found list owamp test servers https://fasterdata.es.net/performance-testing/perfsonar/esnet-perfsonar-services/esnet-owamp-hosts/ 

I have successfully telnet and owping some of servers from list, so it seems my problem is somewhere on server side.

Thanks once more for help. :) 

Best Regards

Miki

2015-12-23 19:19 GMT+01:00 Miki <>:

Thank you very much for this extensive answer :) 

Tomorrow i will try and write about progress.

Regards

Miki

2015-12-23 19:08 GMT+01:00 Daniel Doyle <>:

On Dec 23, 2015, at 12:12 PM, Miki <> wrote:

Dan, 

Thanks for answer. Firewall table is empty and all 3 chains are set to ACCEPT.

Sounds like it's not the host firewall then. As a side note, you probably want to configure that anyway to not be allowing everything as a safety precaution, but that's up to you. There's a good writeup of the various ports pS services use here: http://www.perfsonar.net/deploy/security-considerations/#Using_perfSONAR_with_Firewalls

I've got testing port numbers from admin, but i forgot to add them in owping command. 

Now i have another message: 

"owping: FILE=owping.c, LINE=1598, Unable to open control connection to $destination_host".

Now it is connected to router which is connected to a modem. Tomorrow i will try to connect device directly to modem, to get public IP, and i will write results.

If you're behind a NAT that sometimes makes testing not work properly, though you can sometimes do tests from behind the NAT *to* the target (just not usually the other way around). I would suggest getting a public IP address generally though since it eliminates that as a point of failure.

telnet command is being timed out. But admin told me that everything is checked, i should be able to connect. 

You are unable to reach port 861 on the target machine, so something along the path is filtering it. In the kindest sense, it sounds like your admin is wrong based on empirical evidence. :) Or might be wrong - the problem could be between your house and your place of work so it might look good as far as they can tell at the work network layer. 

Judging from the above about firewall on the Pi itself it sounds like that is not it, so the most likely guess I have is a router ACL at work or maybe even your home ISP. I can't really help you much with that though, unfortunately. Once it is working, you will be able to telnet successfully.

Do you have in mind what can cause error "Unable to open control connection" ?

See above, it means it can't talk on port 861.

Thanks,

Miki

2015-12-23 15:45 GMT+01:00 Daniel Doyle <>:

Miki, 

Maybe a dumb question, but have you verified that the firewall rules either on the machine itself or along the way to the machine on your faculty network are allowing that port? You will need both the control port and the test ports allowed, which are typically 861 for control and 8760-9960 for testing.

A quick "telnet $yourhost 861" from home should reveal whether or not you are able to talk to the owampd process from home.

-Dan

On Dec 23, 2015, at 9:02 AM, Miki <> wrote:

Greetings, 

I have some problems with owping and would appreciate some small help.

I have faculty project to test owping on RaspberryPi. I have owampd process started on computer on faculty network, and i managed to owping it RPi was also connected to that network. 

But, when i try to owping it from home, i get message:

owping: FILE=protocol.c, LINE=1758, _OWPReadStartAck: Unable to read from socket.

owping: FILE=owping.c, LINE=200, Session Failed!

To note, i have started ntp process, but i didn't connect clock source yet (like it is stated in manuals), because i think clock is needed only for better results. Or i am wrong?

Thanks for your time

Greetings

Dan Doyle

GlobalNOC Software Developer

1-812-856-3892

Dan Doyle

GlobalNOC Software Developer

1-812-856-3892

2015-12-23 19:08 GMT+01:00 Daniel Doyle <>:

On Dec 23, 2015, at 12:12 PM, Miki <> wrote:

Dan, 

Thanks for answer. Firewall table is empty and all 3 chains are set to ACCEPT.

Sounds like it's not the host firewall then. As a side note, you probably want to configure that anyway to not be allowing everything as a safety precaution, but that's up to you. There's a good writeup of the various ports pS services use here: http://www.perfsonar.net/deploy/security-considerations/#Using_perfSONAR_with_Firewalls

I've got testing port numbers from admin, but i forgot to add them in owping command. 

Now i have another message: 

"owping: FILE=owping.c, LINE=1598, Unable to open control connection to $destination_host".

Now it is connected to router which is connected to a modem. Tomorrow i will try to connect device directly to modem, to get public IP, and i will write results.

If you're behind a NAT that sometimes makes testing not work properly, though you can sometimes do tests from behind the NAT *to* the target (just not usually the other way around). I would suggest getting a public IP address generally though since it eliminates that as a point of failure.

telnet command is being timed out. But admin told me that everything is checked, i should be able to connect. 

You are unable to reach port 861 on the target machine, so something along the path is filtering it. In the kindest sense, it sounds like your admin is wrong based on empirical evidence. :) Or might be wrong - the problem could be between your house and your place of work so it might look good as far as they can tell at the work network layer. 

Judging from the above about firewall on the Pi itself it sounds like that is not it, so the most likely guess I have is a router ACL at work or maybe even your home ISP. I can't really help you much with that though, unfortunately. Once it is working, you will be able to telnet successfully.

Do you have in mind what can cause error "Unable to open control connection" ?

See above, it means it can't talk on port 861.

Thanks,

Miki

2015-12-23 15:45 GMT+01:00 Daniel Doyle <>:

Miki, 

Maybe a dumb question, but have you verified that the firewall rules either on the machine itself or along the way to the machine on your faculty network are allowing that port? You will need both the control port and the test ports allowed, which are typically 861 for control and 8760-9960 for testing.

A quick "telnet $yourhost 861" from home should reveal whether or not you are able to talk to the owampd process from home.

-Dan

On Dec 23, 2015, at 9:02 AM, Miki <> wrote:

Greetings, 

I have some problems with owping and would appreciate some small help.

I have faculty project to test owping on RaspberryPi. I have owampd process started on computer on faculty network, and i managed to owping it RPi was also connected to that network. 

But, when i try to owping it from home, i get message:

owping: FILE=protocol.c, LINE=1758, _OWPReadStartAck: Unable to read from socket.

owping: FILE=owping.c, LINE=200, Session Failed!

To note, i have started ntp process, but i didn't connect clock source yet (like it is stated in manuals), because i think clock is needed only for better results. Or i am wrong?

Thanks for your time

Greetings

Dan Doyle

GlobalNOC Software Developer

1-812-856-3892

Dan Doyle

GlobalNOC Software Developer

1-812-856-3892