perfSONAR User Q&A and Other Discussion

[Daniel Doyle <>]

Hi Mike,

Sorry if this is a dumb question - when you say "they are now all private", 
does this mean you re-addressed them into RFC1918 addresses? Seems like doing 
that could have caused some different ACLs to come into play, or otherwise 
just made them unroutable from one to another if they are in separate private 
networks. perfSONAR today doesn't really work in a NAT'd environment very 
well.

If you log into one are you able to initiate tests manually? Something like 
"bwctl -c $other_private_address" from one of the newly addressed hosts.

-Dan

> On Feb 8, 2016, at 4:36 PM, Michael Reece 
> <>
>  wrote:
> 
> We had a working perfSONAR mesh setup and the MaDDash and everything
> was working fine. Some of the nodes were on a public network and my
> boss wanted them to be private. They are now all private, but all of
> the nodes changed seem to be unable to run tests with one another. All
> of the affected nodes have the "Unable to retrieve data" orange color
> on the MaDDash grid. I've looked into the YAML configuration file for
> the MaDDash, but whenever it references a node, it does so by hostname
> not by IP address. I don't understand why switching from a public to
> private network would affect the nodes. I am able to SSH into all the
> nodes fine, and also able to access each node's toolkit. Any help
> would be appreciated.
> 
> --Mike Reece

Dan Doyle
GlobalNOC Software Developer
1-812-856-3892

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail