yip reboot has fixed sip logging and appears to have fixed the time.

its a pc engines wrap i am pretty sure its 128 MB.

Also check out http://wiki.pfsense.com/wikka.php?wakka=BootTroubleShooting

FAQ.  Please search before posting.

http://faq.pfsense.com/index.php?action=artikel&cat=4&id=89&artlang=en&highlight=m0n0wall

Thanks for the clarification.  I figured ALL the files/binaries were self contained within the tarball but your explanation makes sense (and I can see why that would not be the case)  :)

My apologies Hoba.  I will keep it in the mailing list.

If it runs on the native hardware but won't work inside the vm on that hardware this is a vmwareproblem. I'm using vmware server with pfSense on athlon64, dual PIIIs and centrino systems without problems (only for developement and testing). I think there is nothing we can do at the pfSense site to fix this.

The swap partition is optional. If you put enough ram in the box you won't need it. Of course enough ram depends on load and used packages.

Or simply reinstall / reflash.

Reinstall / reflash.

Thanks.. i have now just installed the system using option 99 from the livecd menu.. everything work just fine :)

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...