Ran the above full update from the 20100122 snapshot to the 20100203 snapshot and got the following in the bootup screen:

Fatal error: Call to undefined function local_sync_accounts() in /etc/rc.bootup on line 228

Boots up to console setup screen after that with proper WAN IP but there is no access to internet or LAN IP from any LAN workstation.

Apparently this is related to this commit:

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/17fdcb8dc3d9b9f5fb75382207c79387e8ff88ac

Looks familiar from this post

http://forum.pfsense.org/index.php/topic,20360.0.html

Try enabling or disabling device polling from your current setting.

In the webGUI System/Advanced in the Miscellaneous section

And some more reading: http://forum.pfsense.org/index.php?topic=16236.0

Nothing new over the weekend or Monday.  Still waiting on trying some new snaps   

Snapshot server is still pointing to 8_1 though with that Jan 25th snap mentioned above being the latest.  Firmware update to the default 8_0 through the webgui is showing the latest snap of Jan 22nd so the snapshot server has been down for some time now.

If you're comfortable using OpenDNS servers for DNS then you can setup an account with them to block out Social Networking sites but this will block more than Facebook, it will block out MySpace amongst others.

Seems stable enough but like Slam stated above, noticed a huge amount of collisions and errors on all interfaces.

Must be related to OpenDNS and the Dynamic DNS Client only.

My DynDNS (Dynamic) is working with the cached IP showing properly.

Is this one of those serial boot only images? I want to boot it VGA + keyboard. What am I missing here?

Yes, NanoBSD defaults to Serial console.

Windows might be blocking your connection.  Disable Windows Firewall on your client and see if it connects successfully.

?

In the GUI, Interfaces/Assign there is a X button to the right of each interface except for WAN.

Looks like what fixed it was unchecking the 'Disable Auto Added VPN rules' AND setting up the AON.

AON is required when using the redirect-gateway option so there is no advantage/disadvantage.

Since you are using AON, undo the OPT1 tun0 interface.

Post your OpenVPN logs on your pfsense box and also your connection logs on your OpenVPN client so we can see whats going.

From what I've read, you followed the tutorial to the letter including using the exact IP networks?

In the GUI, go to Firewall/Aliases and you can make aliases for the port(s) you want to have custom names to.

Did you check on the server the checkbox
"Dynamic IP"
--> "Assume dynamic IPs, so that DHCP clients can connect. "
?

Suggested that above   

You need an Advanced Outbound NAT rule in place with the virtual Tunnel network as the Source address.

Firewall/NAT/Outbound