Justin C. Sherrill

The reason you can't access dragonflybsd.org is that the network path taken
from your network connection to DragonFly is not being routed correctly.
The traceroutes from before show that one of the network hops isn't
passing along data correctly.  There's not much you can do directly.

The reason that add-on work is because it's taking your attempt to connect
and routing it through another location to make it anonymous, and whatever
path it takes from there is one that isn't affected by the same problem as
your normal traffic.

The backscatter thing has nothing to do with it; it's a (inaccurate in this
case) spam registry.

How is the binary repository built up?  I think you were using poudriere,
but if so I assume it's not the same version that is available from the
etoilebsd.net site.  I'd like to try building a large chunk of packages and
testing installs/etc, especially to compare to the pkgsrc bulk build
process.

Read more »

I tagged release 3.2.2:

http://lists.dragonflybsd.org/pipermail/commits/2012-Decembe[..]

There's a bunch of bug fixes in there so it's a recommended update.

The ISO/IMG files are up now on the mirror-master sites, so they should
propagate out over the next 24 hours.

If you have an existing system you want to update:

As root:
cd /usr/src
git branch (this should say at least * DragonFly_RELEASE_3_2)
git pull
... then follow the normal instructions in /usr/src/UPDATING

If you do not see * DragonFly_RELEASE_3_2, you need to create the local
branch and check it out.  This is probably only going to happen if you
aren't actually on 3.2 yet.

git fetch origin
git branch DragonFly_RELEASE_3_2 origin/DragonFly_RELEASE_3_2
git checkout DragonFly_RELEASE_3_2
git pull

These directions are written without testing, so be careful.