@danswartz:

No offense, but I don't think you will get a lot of free troubleshooting with installing an old, obsolete release for a problem which is only theoretical in your case.

You can even take the "in your case" part out, where ever that info is coming from is wrong - QoS hasn't changed since before 1.2.1 release, same config code in 1.2.2 and 1.2.3, no diff aside from the minor FreeBSD version change which didn't change things related to that.

To install on something with less than 2 NICs, just type "exit" at the prompt to assign LAN.

Yeah either way can be tricky in that situation. If you can't find your null modem cable you can still go the other route.

http://doc.pfsense.com

version 1.2.1 does the same. versions later than 1.2.2 all fail to mount the cd on boot. Same symptoms when booting monowall.
device names tried:  fd0, fdc0, disk0, /dev/fd0  all fail.
must be a bsd thing.

@mhab12:

Nothing special to do besides make sure that your LAN subnet is different from the WAN subnet - i.e. set your lan to 10.21.x.x

thanks for the reply! Works like a champ. Second pfsense rollout and everything went well. Man i love this distro!

I've got a couple installs on InnoDisk IDE DOMs running full installs, and my home testing install which gets reinstalled frequently from 2.0 snapshots. All of these have been stable running for at least 18 months, the oldest is about 24 months with no issues. Industrial flash is designed to be used this way, I doubt you'll have any problems with proper industrial flash modules, be it CF, IDE/SATA DOM or SSD.

You do need to disable DMA, this is what I id with 1.2

FYI though, 2.0rc does not install on microdrives with CF adapters and just bombs with geom errors :(

Super Secret Trick: type "exit" at the network card assignment prompt and it will continue through to the menu

Though pressing 'i' at the install/rescue countdown prompt early in the CD boot will work too

pfSense is a "stand alone" OS.  It uses FreeBSD as it's base.  You install it on it's own real, or virtual, machine.

Cheers.

It could be something specific to that disk or BIOS.

You might try to do a low level format of the entire disk before installing to see if that makes any difference.

Thank You! I was able to install the upgrade with no problems…Jon

It's fine to go straight from 1.2 to 1.2.3. The only potential area where you may run into a snag is if the updated FreeBSD base is problematic in combination with your hardware for some reason, but that's a tiny minority of cases, so you should be fine.

The Cisco bit is especially irrelevant because someone earlier in this thread posted a solution for the bug and you could edit the file on your own system to fix it. Try that on a Cisco box. :-)

Just because a whole new release isn't going to happen for a few minor bugs isn't a big deal when they can be patched manually by anyone who really hits them.

https://rcs.pfsense.org/projects/pfsense/repos/mainline/logs/RELENG_1_2

glad I could help out!

Bravo.  That did it….Working now.  Now, as you said, just need to tighten it up a bit.  Thank you for your assistance....

Just to update. I installed 2.0 beta and it works fine. It recognizes the integrated card and it has not crash (trap error).

Thanks

There are people who want to run a full install on an embedded system.  Typically these are people who've put microdrives into embedded systems instead of using flash.

Thanks for the tips, especially device.hints … but, you're right, there doesn't seem to be any reference to USB drivers in there.

I can live with USB being enabled, since one has to be root to mount anything, but I prefer to "tie up loose ends" when configuring security devices.

You don't say this, but I'm guessing you don't want to install to the internal hard drive. Why?

I suspect it will be difficult to successfully boot with a non FreeBSD component (Plop - I've not heard of it before) in the boot chain since its probably unaware of the FreeBSD boot component conventions.

If you are trying to avoid using a rotating drive I suggest you try using a Transcend DOM. These are solid state drives intended to replace IDE or SATA drives and are available quite economically for sizes of 1GB and 2GB.  A couple of sources: http://shop.transcendusa.com/product/ItemDetail.asp?ItemID=TS1GSDOM22V or http://www.memoryc.com/transcend/ts2gsdom22v.html I have been using a 1GB IDE variant of these drives in my home pfSense for over 2 years now. I purchased mine from memoryc since I don't live in the USA.

From my experience, RC3 was not really a viable option for upgrading to the release version if you want future upgrades to work (this was on the 512mb build, in case the size is relevant to the failure).  I could upgrade to the release version, but the next time I tried to do an upgrade to anything, it would fail with an error (some error with writing to /etc/fstab I think).  It also lost the ability to change the default bootup slice for the same reason.  I've had no issues upgrading from a card starting out fresh with the 1.2.3 512mb image, however.  If you fill up the drive too much with packages, it could also interfere with upgrading, as far as I know.