From Jeremy Porter on the dev mailing list, in response to an email query about the missing pfsense-tools repository:
We are in the middle of migrating repositories and services to new hosts and datacenters, to support our work on pfSense 2.2.
I really don't think they are going to make pfsene-tools closed source! You guys have been reading too many posts in the "NSA" thread
And they do have to protect the pfSense brand - even I, with absolutely no financial interest in ESF, do not want images built and publicly published with full pfSense logos etc that have real problems. New users will end up finding them accidentally in searches and will install them thinking they are good-to-go. Then they will psot on the forum and... As I understand it, FreeBSD10/pfSense2.2 in its current state is really not useable by anyone other then real dev-nerds, for development purposes only. In that case, it really is best that there not be public images available yet. People who really want to join in at this stage of development can build it all themselves or contact ESF and really make an offer to contribute their time/skills to work together with the other devs on driver issues, patches and...
But it would have been nice if ESF had posted here first, letting everyone know the repository would be off-line for x time, rather than letting a thread like this develop.
I was also looking at apinger and the patches to it in pfsense-tools just to see if I could spot what might be causing the varied latency and packet loss figures that happen sometimes.