Hello, I've just finish to copy an img to a CF (from Debian) no problems… dd if=pfSense-1.2.3-RELEASE-4g-nanobsd.img of=/dev/sdg 7827687+0 enregistrements lus 7827687+0 enregistrements écrits 4007775744 octets (4,0 GB) copiés, 3947,2 s, 1,0 MB/s

There aren't any automated conversion scripts out there, but usually it isn't that difficult to go through and convert by hand into the GUI. You can probably drop a lot of that length by proper use of aliases and such.

Any ideas?

A good chance is that there was a NIC duplex mismatch, which causes the packet errors you see and screws your perfomance to the wall.

When it's ready  :) Hopefully sometime before the end of the year. PPTP/GRE NAT issues are still there, I'm not sure if there is still a chance they'll be addressed or not.

thanks everyone for the input i will go ahead with the 1.2.3 until I'm more familiar with pfsence.

Thanks for reporting back. Bit of a trap that auto-detect and the firewire interfaces.

Yeah that page is WRAP-specific, not applicable to the ALIX at all. If you're seeing that, you have an outdated BIOS on the ALIX that has a bug that prevents it from functioning. Upgrade the BIOS and you'll be set.

However, you can do a full install onto CF, which is what the OP asked about.  There are just things to be aware of, all of which can be easily found by searching the forum.

You are both right, it seems that some one pulled the plug on the pfSense box without telling me. I am glad its not a hardware failure. Verified by pulling the plug on the system, all RRD info was erased. Thank you!.

I put some stuff at the bottom of the rc file and it is all working now.

On the console, you get a menu. It's one of the menu options. Just look at the list, press the number, and follow the prompts. No commands to type. :)

I presume you have the problem described in http://forum.pfsense.org/index.php/topic,25444.0.html  If so, follow those instructions. When you installed on USB the drive would have been called something like da0 but now that its connected to a SATA controller its called ad6. The startup just needs to be tweaked to look for the root filesystem in the correct place.

There isn't really an easy way to move the configuration from opt1 to WAN if you want to keep the OPT1 rules and make them the new WAN rules (discarding the current WAN rules). You might have to hand-edit a config backup and replace opt1 with wan in the rule interfaces, but it would be easy to mess something up so be very careful (and keep some clean, unedited backup copies).

It works! Many thanks, you saved me a lot of time and trouble. :)