HP DL380 G3 and G4 runs well.

Thanks for your reply.  This is what I have

MEMORY

**[/var/log]cat dmesg.boot | grep memory

real memory  = 1072562176 (1022 MB)

avail memory = 1035730944 (987 MB)

**PROCESSOR  **  
[/var/log]sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu'
hw.machine: i386
hw.model: Intel(R) Pentium(R) 4 CPU 3.00GHz
hw.ncpu: 2
hw.machine_arch: i386
[/var/log]

PACKAGES

bsdinstaller-2.0.2009.0422 BSD Installer mega-package
grub-0.97_1         GRand Unified Bootloader
iperf-2.0.4         A tool to measure maximum TCP and UDP bandwidth
libosip-3.1.0       A low layer of SIP implementation
openbgpd-4.0        Free implementation of the Border Gateway Protocol, Version
siproxd-0.7.0_1     A proxy/masquerading daemon for the SIP protocol
zabbix-agent-1.4.5,2 Application and network monitoring solution

Thank you for your help. Finally I have gotten rid of that stupid FATAL ERROR MESSAGE.  All I had to do was to edit /etc/inc/config.inc and change the 32M to 256M now it is working the way it is suppose to.**

I had one other problem getting my microdrive/Atom combo working that may be relevant here.
I noticed after much hair pulling that although my CF reader was configured for master (no jumper installed) it would jump to slave after a soft re-boot.
I would power the router on USB DVD Rom installed microdrive seen as master,
Install pfsense then on the soft re-boot at the end of the install the CF/microdrive would suddenly change to slave. As the install was performed to master it would boot all the way to the mount bit and fail, just like in your case. I think I could still force it to boot by telling it the new location by issuing something like;

mountroot> ufs:da0s1b

To fix the problem all I did was install the jumper on the CF reader so that the drive was always slave and would not jump about. I also mailed the supplier of my £200.00 board and they said no it must be your CF reader although if you look at these things there is really nothing to them.

Just a thought!

Time has passed and I have another dead USB flash drive. Again I installed from the live cd (pfsenes 1.2.3). This time I selected the embedded kernel when the install script asked me. I believed I would get an embedded installation by doing so. Anyway, there were obviously enough write accesses to kill the flash drive in the end.

Each VLAN will be an interface, and the current stable version only supports traffic shaping between two interfaces.

@dothoe:

I downloaded, and burned pfSense-1.2.2-LiveCD-Installer.iso. I put it in the computer I plan to use as my firewall. According to all the docs I can find here I'm supposed to select option 99. The trouble is that I only get 7 options which are:
1. Boot pfSense [default]
2. Boot pfSense with ACPI disabled
3. Boot pfSense in Safe Mode
4. Boot pfSense in single user mode
5. Boot pfSense with verbose logging
6. Boot pfSense to loader prompt
7. Reboot

How do I do an install? Did I get the wrong ISO?

Thanks,

That menu is essentially the options for the boot loader. Like options for safe mode with windows, or options for single user mode for Linux using grub or lilo.
Just let it boot normally and you will see the options after a successful start-up.

@macsta:

thanks wallabybob for the response.

I've decided to do a full-install on my flash device, and change the setting "pfSense" to "embedded" and it has detected the USB wifi dongles fine.

Now onto stability testing on the VIA chipset.

Cheers

you mean when it asks you which kernal to install??

im currently having the same issue and don't want to install a hard drive.  its nice and quite without one.  i assume you turn off the swap and disable logging as well to minimize the writes?

Nevermind, idiot here.  Came home, plugged it all togther properly, disabled dhcp on linksys, enabled it on pfSense and I'm srfin from home ;)

Thanks again all

-Marty

Today I remotely upgraded our primary firewall to 1.2.2.  It didn't came up anymore.  I went to the datacenter and it was just hanging in the boot sequence.  I have taken some information and will verify this tomorrow with the vendor.  As the bios version is the latest.

So it is definitely a problem with freebsd 7.x and supermicro hardware.

Thanks everyone

I'm using pfSense-1.2.3–20090718-2234-nanobsd.img.  Would I be right in thinking this version will default to vr0 and vr1?  I have tried connecting to each of the 3 ethernet ports and it appears DHCP is not active as I get no IP address.

Elliot

ahh sorry i mixed up the story :P

WAN was 62
lan was 192.168 numbers sorry to mislead you.

the poblemen was the NIC i had an other old one. and now everything works ;)

We had the same problem. Changed to Intel NICs and it has been running for 6 months now.
Check your hardware.