perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

My apologies...

I have been creating some test perfsonar instances for a workshop, using 
unroutable RFC6598 address space (100.64.0.0/10) - these are basically 
private addresses but they look like real ones.

Unfortunately it seems these test instances have ended up in the global 
services directory, with addresses 100.64.0.200-206.

I've now disabled the registration daemon, but you may want to purge 
this junk out of your database - I don't know if it auto-expires, and if 
so how long that takes.

I notice a few RFC1918 addresses in the database (e.g. 192.168.20.192, 
192.168.7.153), so it might be worth having a filter to exclude those 
and other unroutable addresses.

There is a wider issue which I expect you've already considered: whether 
it would be better for perfsonar nodes to register themselves only when 
some of the host administration information has been configured, because 
at the moment it seems to be registering immediately even when this is 
all blank, and with a node access policy of "public" pre-selected.  This 
means that the moment you create a new node on the network you may be 
unwittingly inviting people to use it, even if this wasn't something you 
intended.

Having said that, I acknowledge that the majority of perfsonar nodes 
*are* intended to be discoverable public resources, and you don't want 
to make it any harder than necessary for this to happen.

Regards,

Brian.