It's in desperate need of some formatting.  Download a few professional manuals or guides and take some notes on how they look.  Pay attention to: Font faces & sizes General layout & spacing Chapters or Headings Make your title font size larger than the body text, and BOLD it or something to make it stand out. Also, don't link to the i386 build since it's being deprecated. Do as John says and use a virtual machine so you can create clear screencaps instead of fuzzy photos with flash flares. Don't put your images inline with your text or it just looks like a jumble. VLAN, not Vlan. I could go on, but the major thing seems to be you're installing in one particular way and you don't talk about other options.  Any time the user has some sort of choice, you need to explain the available options and what they mean instead of just saying "Do this", when it may not apply to that user.  For example, you say to enable DHCP on LAN.  That can cause major problems if the user already has a DHCP server.

Happened to me on a fresh install posted in this thread.  https://forum.pfsense.org/index.php?topic=92712.0  Not an upgrade but a fresh install.

Ah ok =) Anyway. This isn't really a problem anymore for me. I know what caused the issues now. Therefore i would like to take this opportunity to thank everyone who has been helping me out with this issue =) Thanks !

Those are the ones you give out to people you don't like when they ask for a flash drive to "borrow" :-)

^ yeah is this script in clear text?  Sounds like bad idea to me ;)

There was an issue with the update .tgz files that should be corrected now. Forcing another update to the same firmware should be OK, or a wipe+reload is always a solid path to success.

Interesting. So it appears the ale(4) driver was causing problems for fragmented packets. Thanks for posting that. Steve

Thanks a lot for the hint Gertjan!

There is no 8GB nanoBSD image built. Install the 4GB image. It will use the first 4GB of the 8GB CF card. The last 4GB will be free. Who cares? Dansguardian (becoming E2guardian) and Squid (as long as you do not want to cache) run on nanoBSD. If you are going to do Squid caching then you need a full install. Some packages are not supported on nanoBSD - to see which are not supported you can look in https://github.com/pfsense/pfsense-packages/blob/master/pkg_config.10.xml - search for "noembedded" to find packages that do not install on nanoBSD.

Upgrades should go fine - the vr* interfaces are already in the config of the upgraded system. I have upgraded 10 Alix 2D13 to 2.2.2 all without trouble. The change to factory default behavior is documented in just 1 line I can find: https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes Change default NICs from vr to em – vr is on the way out and em is the most common NIC in use today. A reader needs to already know a bit about pfSense and default interface assignment… to understand the ramifications of this 1-line statement  :)

Uhm… perhaps it would work better if you changed your PC's IP address as well to match the pfSense LAN subnet. Or perhaps enable DHCP? Or maybe just try again so that you can tell us what exactly you have done, since you apparently cannot even remember? Sigh...

@jailbreaker: added the next 3 lines hw.ata.atapi_dma="1" hw.ata.ata_dma="1" hw.ata.wc="1" This has no effect on 2.2.x, read the wiki for proper hints.

Ah, I didn't know BIND was a package now.  Got rid of that tiny-dns thing and installed BIND.  Looking good and I actually have the features I wanted.  :D Still no go on the arpwatch front, but whatevs.  I will deal with it.  Thanks for all the help!

So I figured out a hilarious workaround for this and I'll post it here so maybe I can help a brotha out… I downloaded VirtualBox on my Mac and installed pfsense to a qcow image and immediately powered it off. Then I copied the qcow image to my host, converted it to qcow2, then re-ran my virt install command. It boots now :)

Kool…...seems to be the best method of upgrade. That way "little surprises" don't bite ya on the can. Going to order a new CF card here to use for "Upgrades"....burn the new one, restore the config.xml file. The autoupdate is a .........well...........rough around the edges. Glad it worked.