Sounds like you're probably exhausting the state table, check your RRD graphs to see, and try increasing it.

Thanks very much for your help wallabybob, but I am going to have to cut my losses as it were and stick with the Smoothwall. Maybe when I have learned a little more about linux (or when freebsd recognises the fit-pc) I will have another go. Cheers.

Hi. I've uploaded both 1.2.1-latest and 1.3-latest onto my old LV-673 with Pentium-M. As far as I have done for both CF/HDD installations for both releases, only the differences are that I don't use CF-IDE things, and my CF is only $7 512M bytes crap, other than that I don't see any differences between embedded and full(?) images, both detect on-board stinky Marvell NIC just fine everytime, whatever kernel is installed. I wrote embedded to CF on Vista. cheers,

Good for you  ;) ;) ;)

@lklaus: Well, if you don't expect a conflict with your internal addresses, you can boot the alix board and add a virtual ip to your interface (I added 192.168.1.2 to eth1:1 [linux]) and could talk to the board via the webgui The problem is, at least with pfSense, that the interface on the Alix will not be up until you complete the 'assign interfaces' dialog via the serial console… The pre-loaded boxes from Netgate may already have this done, I'm not sure.

Hello, http://forum.pfsense.org/index.php/topic,11049.0.html :D :D :D :D :D

Congratz, and welcome!  ;)

Google for FreeBSD BTX boot scsi shows a history of people having trouble doing a FreeBSD install with SCSI drives in the system and the problem appears to be in BTX. I suggest you disable your SCSI controller, add an IDE drive to the system and attempt to install onto the IDE drive.

When I boot the pfSense install CD the console output does pause at that point for a few seconds then carries on. I suggest if it pauses more than (say) 30 seconds you give us a bit more information about what you are trying to do so we have something more specific to work with: What version of pfSense? Is the CD drive an "internal" (IDE) drive or external (USB?) What type of system: CPU, memory, drives, NICs?

Thanks for that. I'll try one of your suggestions tonight. Just for your, or anyone else reading's, information. The machine is an AMD Athlon XP 3200+ on an ASUS A7N8-E Deluxe ACPI BIOS Rev 1013 (Nvidia nforce). With Phoenix Award BIOS v6.00PG.

@cheesyboofs: Hi Chris, Great stuff! You say you where able to test 1.2.1 with spamd, where you able to confirm it working on 1.2.1 before you went back to 1.2, because I'm having a little trouble. http://forum.pfsense.org/index.php/topic,11044.0.html Out of all the pfSense features the spamd plug-in seems to be one of the simplest to configure and I'm not exactly a moron but would you give my post a quick perusal and see if you can spot anything obvious. Cheers Never got far enough to send traffic through it to be honest, so, mine could have had the same issue, it appeared everythiing was right, but again, didn't get to send traffic through it.. sorry!

As every other post on the issue of release dates has said - it'll be released when it's released ;) As far as whether or not it is suitable for use, only you can really decide - read the forum and see if the problems people are reporting are, for you, showstoppers.

Why dont you install the full version? To avoid death of the CF due to repeted writes, you "could" install the full version and then change it into the embedded. This is not officially supported, but seems to work quite well for a number of users. –> http://forum.pfsense.org/index.php/topic,6469.0.html howto --> http://devwiki.pfsense.org/FullInstallOnWRAP

I don't know the internal working of pfSense in this regard so the following suggestion might be way off the mark. WAN and LAN interfaces seem to have a special meaning in pfSense and possibly some special "hidden" firewall rules. Can you add  or configure a third interface to this box? It will default name to opt1. Then bridge opt1 and LAN and leave WAN unconnected (so connect your previous WAN to what you now call OPT1). Probably not optimal but you wanted something in a hurry. I have a wireless LAN configured this way and it seems to have been working fine for a couple of months.

Found the problem. These cisco devices have a simm card in them that it tries to boot off. Pulled it out and now all is good.

so it is possible to make a clustering . sounds nice  ;D

Nice, 1.2.1 detected all of them