Does your client have the pfSense LAN IP address as the default gateway? (If the pfSense LAN address is assigned by DHCP then its possible it could change so you need t consider how your clients will change their default gateway in sympathy with the pfSense LAN interface IP address. If you use DHCP on your LAN I think things are easier to manage if pfSense is the DHCP server.)

My Old Router is using (192.168.0.1) but I disconnect it in the net system and.. I also connect the lan cable directly to the 2 PC to try, but no success… -Is there a color code standard in utp cable on PFsense... PFsense Guide on PPoE Type Wan... I always get no link-up on WAN interpace..

@jimp: 2.0 is based on what will be FreeBSD 8.1. A major difference from 7.x in many regards. Ah - that was good news indeed. OK, we'll give it a whirl once it's been released and see how it goes. Best regards, Anders C. Madsen

I am using the same server to get started with Pfsense. So far I have not been able to get 1.2.3 loaded, it hangs and the keyboard doesn't function. I have been able to load the ver 2 June 15 beta but it returns a syntax error when choosing menu items. If you could let me know if you had similar issues and what changes you made to get it functioning I would appreciate it. Thanks, Mike ???

Sounds like you are on the right track. I've never used a firebox but I've done the same thing on a Symantec 5420 which is in another thread on here and the wiki. Steps are likely similar. Everything should be detected and you'll see output on the serial console.

Hadn't seen your post Just one word to thank you. Guillaume

Ah, that would explain why I couldn't find the option. I turned off the machine and fully reinstalled and it seems to be working correctly now. Thanks for taking the time to help

what you were probably reading about is how kingston is using cheap memory modules for its flash drives and they are having a high failure rate. m0n0 is a lot smaller footprint (10-20MB), it does not take up the same amount of space as pfSense does and as a result wont hit 2020163584 bytes. pfSense requires 128MB minimum. and the current smallest image (for 1.2.3R) is 512MB, which is about 500MB more than m0n0. from the total bytes you are writing the 1GB image to the card, m0n0 is only writing .02 GB at the most, the card is probably bad.

Thank you master, you were my only hope. :) That concludes my first newbie-question. Thank you again. It all works as I intended now. +1 for you GruensFroeschli.

As long as you put an OS on the USB to boot from, together with a program to copy the image to the CF, and the system you're installing on can boot the USB, then you're good to go. That's exactly how I load my system. Cheers.

Like most cheap "RAID" controllers the Promise card is little more than a dual port SATA controller - the mirroring is handled by the drivers Promise provide (also known as fake-RAID).

Got it. Thanks

@jimp: It might be crashing during the boot process. You might try to disable some things in the BIOS as a test, such as ACPI Or try some of the many other suggestions here: http://doc.pfsense.org/index.php/Boot_Troubleshooting cool after disabling the ACPI it work's fine :) Thanks

After chastising the new addition of the PFsense box into a network that previously worked un-flawed, I have finally located the intermittant problem (everything works when I attend site). One of my access points which has sat happily for years on the network without the PFsense box decided to give up - it would allow wireless connections but no IP from the PFsense box could be issued as the LAN side of the access point would not work. Another case of hardware issues.

@Efonne: Those NanoBSD images currently only use a serial console and do not have VGA support. That was, of course, the problem - thanks a lot! Probably it would be nice to document that on the Download and Versions pages.

There are no publicly available scripts that I'm aware of. It shouldn't be too difficult to do it line-by-line by hand, however.

No - you don't need to have any network cables connected. Can you provide: The exact version of pfSense you're running (eg 1.2.3-RELEASE nanobsd) Exactly what the problem is (so far, all we know is "it doesn't work")

I currently have two ALIX 2D3 running 1.2.3 Released with no problems.  I would try reflashing with 1.2.3 and if the problems still persists, save the aluminum case and throw the motherboard in the trash.  BTW, have you tried another power supply? Roy…

Thanks jasonlitka. Looks like that is it then…. Looks like it won't be in FreeBSD 8.1 either (pfsense 2.0).... Time to go and buy another NIC (or look at another FW disty) Thanks all for quick response to my original query.