I have been recycling my config file since BETA 5 with no issues.  I would do fresh VM builds every so often in between updates.
From my experience, it has been solid for restores from build to build.

I have a basic config with nothing fancy on the routing and networking side.  Just some nat's, aliases, rules and some settings, but way too much to redo from build to build.

So for peace of mind and if you want to start fresh, do a complete new build and then make a backup.

Yes, I found that out the [really not so] hard way. But WOO-HOO! the serial connection is up. Unfortunately, I cannot with any degree of surety, point to the change that made it possible.

My suspicion is that either my PC's serial port (which I added on and plugged into the appropriate port on the motherboad), or the null modem cable, was faulty.

For when I went out and picked up a USB to Serial adapter, and new null modem cable… it worked, both with Minicom, and GTKTerm.

I have what looks to be one last hurdle to overcome, but since it's a different issue, I'll start a new thread.

I am also running behind an Untangle server. Thanks you very much!!

Case closed  :)

OK - on permanently it is then!

It always had it, just not the automatic way. :-)

i used a SD to IDE adaptor for a bit, just a cheap one from ebay, crapped out after about 6 months though.

Didnt have to….

tail /var/log/system.log

show me the progress... I just had a lot of pkgs :)

All done.

Thanks.

Sorry, not the modem but pfsense

Updating this thread since it comes up high in Google results - 2.0 release and later now are released including nanobsd VGA versions.

@jimp:

Read the sticky post at the top of the 2.0 board about fixing your update url

http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/.updaters/
worked perfectly for the m1n1wall. Thanks.

In that case I won't take the risk.

Many thanks.

Forgot to mention…
I also tried to install pfsense 1.2.3 (so I can perhaps do an upgrade), but this wont even boot the cd all the way.

As I can get the box for less than £100, it seems a great idea!

There are going to be less than 100 people/machines connecting to the internet through pfSense on a bonded ADSL with about 18Mb in and 1Mb out speeds.  All the users are on separate vLans, so there should be no local traffic going through it.  Monthly internet use is currently downloading about 750Gb/month.

Ok, thank you.

Suggestion:
Try adding the line

kern.cam.boot_delay="20000"

to the pfSense file /boot/loader.conf.local (create the file if it doesn't already exist). This will delay the startup a bit before trying to access file systems. You might need to tweak the number a bit to make it big enough but not "too big".

Thank you very much!

Regards

Kostas

Sort of feasible:
if you have modem in routing mode, then it's feasible
-or-
you have modem at bridging mode and you have not done all the virtual ip's for the pfsense
-or-
you have every single wan ip set, but manual outbound nat rules isn't set right

@GruensFroeschli:

Update your (tiny)BIOS to 0.99h
You can download the needed files here: http://pcengines.ch/alix2.htm

Thank you a lot GruensFroeschli. Now, with the 0.99h bios, it works!!!

Thank you again!!! :)

Luca

To the original poster, just to be clear:

You have added a route on the Cisco router to the pfSense box and a route on the pfSense box to the Cisco router's subnet and all have the correct metrics and other options specified for the two different entries on the two different devices?

Just checking…
Take the best and leave the rest.

Jon