http://forum.pfsense.org/index.php/topic,7001.0.html –> The embedded version does not have any VGA output. Connect and configue per Serial port.

Upgrade the secondary first, then the primary. We recommend reinstalling on the embedded platforms.  We are still ironing the upgrade bugs out.

@cmb: Not when the BIOS has bugs that we can't easily work around, that's why you have to upgrade the BIOS. I'll second this.  We have a pfSense box in production that started out rather randomly flakey.  After some experimentation we checked the manufacturer website and found there was a new BIOS that fixed some PCI timing issues.  Loaded it and everything works great since!

From memory this has come up before - search the forum.

I can confirm this crash also.

You have more than one core so the multi-processor option is probably the best choice.

@MageMinds: I have installed pfSense from the LiveCD onto my 512 MB CF connected using a CF to IDE adapter. I have removed the swap partition and then I choosed the "Embeded Kernel", but in the System Status the platform say "pfSense". Shouldn't it say "Embeded" also I have access to the "Packages" wich from the forum I'm not supposed to be able to install them. I have installed pfSense 1.0.1 from the LiveCD on a CF like you. The trick to convert it to "embedded" is to run this command: echo embedded > /etc/platform and reboot.

I used the windows version of dd to copy my working 128MB CF to an image, using this command: dd id=f: (replace with yours) of=pfsense128mb.img Then I inserted the new 1024MB CF into the USB reader and used physdiskwrite.exe to restore the image. Ofcourse, my 1GB CF is now seen as a 128MB one. My Alix2c3's are now booting from the new 1GB CF cards.

try to use 208.67.222.222 and 208.67.220.220 they are OpenDNS http://www.opendns.com/ and worth a try cheers raylund

Quick Update: I found out what the problem was…..I had to go to Interfaces -->then choose "assign" then choose and add the actual MAC address of the wireless NIC (from the drop down menu).  Once I did that, I saw the actual interface listed as OPT1 (which you can rename it if you like i.e. WLAN). Needless to say, there was one more step left and that was to "Enable" the interface that I had just added.  For some odd reason, I kept thinking that the wireless NIC interface will "automatically" be detected and listed in the "Interfaces" menu (goes to show you how little I know!!) Eventually, I got it working through my wireless NIC. Thanks for the help.

it seems to connect to http port, but there is no dialog … only get timeout telnet pfsense.com 80 Trying 69.64.6.13... Connected to pfsense.com. Escape character is '^]'. GET /index.php HTTP/1.0 On the other wan carp host member i neither receive packets from 69.64.6.13 Also tried this : fetch http://www.pfsense.com/~sullrich/tools/easyrsa.txt easyrsa.txt                                  100% of  736  B 4251 kBps and it works ... whats is the exact url related to packages ?

The minimum requirements page says 128 MB.

I searched the forum and came up short, that is why i asked, but thank you for the response

Thanks Gruens, Exactly what I was looking for. Sorry… noob here!

You should know what you actually need, maybe we can provied some help then. Just because it can be done doesn't mean it has to be done! Why would you want to separate your DC from the LAN clients? You would have to create firewall rules to allow traffic back and forth anyway. If not, then it's not your DC any more and if you do, the separation doesn't make any sense. At least with the information aboout your network we got so far (1 DC and 20 DHCP clients) this is not desirable to do. KISS is your friend! (http://en.wikipedia.org/wiki/KISS_Principle)

RC3 has solved my problems. I even used the SMP kernel! ;D thanks, Ricky