Ahh yes, this is confusing.  CARP at one point was a package and at some point in the future we will start turning base features into packages as well.  This is the reason we did not move the setting back to the base area.  A number of base features will be "packages" in the future.

Since RC3 update I must reboot the fireall every 3 days.
No bridged network from OPT1

How can I see extended logs or debug ?

[]'s

nope i use pfsense to add the patches and extra files to the basic rc3 embedded image

@hoba:

Here's everything for this server: http://www-307.ibm.com/pc/support/site.wss/product.do?template=/product.do?template=%2Fproductpage%2Flandingpages%2FproductPageLandingPage.vm&sitestyle=ibm&brandind=8&familyind=50276&machineind=0&modelind=0&partnumberind=0&subcategoryind=0&doctypeind=9&doccategoryind=0&operatingsystemind=49977&validate=true

My one has 1,2 GB, 1x1,4 GHz PIII-S (512kb cache, second cpu socket not used). 2x 18GB SCSI RAID1. Additional to the 2 fxp onboard nics I have a 4port switchcard that is realtek based in it. The only thing that I had to do to make the live-cd boot completely is to disable dma for the atapi cdrom and disable the fdd in bios or it would halt somewhere on bootup (see http://wiki.pfsense.com/wikka.php?wakka=BootOptions for how to disable the dma mode).

wow that is very helpful! I really appreciate your input and dedication to the community!

I will certaintly give that a try sometime this week.

Yes random it was also halting at the drive detection screen, but sometimes it went through? Also though one of my cards wasnt being detected though on the PCI bus. I had 2 onboard + 2 realteks and only one realtek got picked up.

I will do a bios update and try those settings and maybe report back this weekend.

Again thanks!

@hoba:

When we first tested ntpd with one of my machines (an old k6-2 450MHz) we thought ntpd is not working too. We had to set incorrect times manually to see that it actually is working. Some clocks are just working properly even if you don't expect it  ;)

Sounds good to me !

Yep  ;D

The bootstrap (/usr/local/etc/rc.d/dev_bootstrap.sh) works right now.
Still got a (non significant ??) error when ending the bsdinstaller :

…pkg_create: make_dist: tar command failed with code 256
Creating package /home/pfsense/tools/builder_scripts/conf/packages
Registering depends:.
Creating gzip'd tar ball in '/home/pfsense/tools/builder_scripts/conf/packages.tgz'
*** Error code 1

Stop in /usr/ports/sysutils/bsdinstaller.
Bootstrap completed.

Building iso......
....

but I think I saw this one before - it doesn't stop from building valids …. builds  :)

Thanks for the tip.

that's correct, those updates don't update the version number (though personally, I wish they did, it's hard to tell what you're running otherwise).

thanks a lot  :D

that's what I needed!

srs

@hoba:

Swap partition is optional. You can run without it. Just remove it completely.

Sweet.  Thank you for the response hoba, you kick ass!

Wanted to add in the dmesg log. Looks like confirms its syncing packages twice here as well.

Syncing packages…
Syncing packages:
miniupnpd
.
Executing rc.d items...
Starting /usr/local/etc/rc.d/miniupnpd.sh...

Give it a try. It should work. If not be prepared to set it up from scratch.

You can apply this to embeddeds as well as full installs and you should do so.

This indicates a DNS issue. The service is not able to determine the IP-Adress of the specified Timeserver to update it's time.

i have been using my pfsense box on 192.168.0.1 ip from since beta 4. it works just fine. just need to set ur lan ip on ur pfsense box correctly and are u using the pfsense dhcp server ? if ur setting ur ip manually did u set ur gateway and dns entry to point to ur pfsense box ? if ur using dhcp did u release and renew ur lease after changing the pfsense ip? if done correctly it should work.

Yup that's of course true. You can still boot from CD but store the config on USB I imagine (lot of old PCs not able to boot from USB.) CF IDE sounds nice too. How about CD-RW support LOL?

You can use the nexcom either with the embedded image when running from cf-card (at least 128 mb media required for the recent version) or a full install from hdd.

See http://www.mail-archive.com/support@pfsense.com/msg03811.html for an earlier ml post where I summed up some things about the nexcom 1041c.

i am working on it, think i will have it done until weekend.

best regards
Gino "dairaen" Thomas
http://nux-acid.org

If this is a full hdd install you can just use the recent full update file. If you are on embedded you need to reflash.