If this is a full hdd install you can just use the recent full update file. If you are on embedded you need to reflash.

Unfortunately not.  This is a incomplete bug report. Please provide more information.

Thanks, I commited a fix for this.

No, you should go directly to the latest of the snapshot builds now that you can find in the ~sullrich folder. In case you are on embedded you have to reflash as the RC2x-series builds didn't support the new update mechanism.

I have followed the instructions to http://wiki.pfsense.com/wikka.php?wakka=FullInstallOnWRAP So from last post, i see that there is no way to run full on microdrive. Is there someone i can email about getting a custom build.

Thank you, after changing my /etc/ttys as mentioned above, I can work on the serial console. The only problem I have is that CTRL-C is not working; I see a ^C in my terminal window and the process is not stopped. Any idea about this? Peter

@msatter: :-[ :o ;D The problem is solved and I made a typo in one of the 50 addresses and a "/" was at the end of the IP number. On reload I don't get any warnings anymore to my relief. Thanks for your reply Hoba and I sorry to for any inconvienance on your side caused by my TYPO. Best wishes, Marcel [/quote] I know you've marked this as solved, but where was the typo?  In the alias input screen?  If so, maybe we're missing a validation check that should have caught that. –Bill

cvs_sync.sh is gone. Upgrade through the webgui to the latest snapshot: http://pfsense.com/~sullrich/1.0-SNAPSHOT-09-03-06/ If you are on embedded you have to reflash as these builds need 128 MB partitions. On the other hand embeddeds are now upgradeable too due to the larger partition.

Yes, go ahead and replace the card and boot pfSense.  It should complain about a interface mismatch.  If i it does not then simply reasssign the interfaces and reboot.

Thanks Scott, I tried with a third disk and it finally worked after I enabled  LBA.  Luckily ;-) As of the installer's Keymap select option, is it intentional that there is no selectable countries but the 'default' there? Any other possibilities to assign a national keyboard layout to pfsense..? regards Tor

Use the official RC2 embedded image from the mirrors and run the update scripts.

My apologies.  Edited my post above.  Didn't realize I was butting my head into a flame war.  Wasn't my intention.

During filter reloads and interfaces changes it is true that the console will freeze.  This is part of the remaining Big Giant Lock in FreeBSD where the TTY is still under it.    If you give it a moment to recover or better yet upgrade to RC2e then these problems will go away.

I backed up the complete config, restored it and it wouldn't let me create any more rules. So I'm not sure if it is working… then again, it's been giving me hell today, so maybe its the platform (old Dell desktop).

Thanks, we are working on the issue.  Peter's patch introduced this behaviior trying to fix negated rules. So far it appears to be a cosmetic pf bug but we need to be absolutely sure.  Please test your ruleset inside and out and make sure there are no problems with it. Thanks!

Create pass any protocol any source any destination rules at all interfaces except WAN first (firewall>rules). Then enable DHCP Server for the additional interfaces (services>dhcp, opt1 and opt2 tab). Set your Router as DNS-Server at system>general unless it already is assigned via DHCP and uncheck "override by DHCP" if needed. Then create portforwards at WAN (firewall>NAT, portforward) for all needed services to the servers in the different subnets. Make sure autocreate rule is checked (it's checked by dfault). You might want to check "Register DHCP leases in DNS forwarder" at services>dns forwarder too. Last but not least add portforwards to your router in front of the pfSense to hit the WAN IP of the pfSense for your different services. This is a double NAT setup and therefor doesn't need any routes. If you rather want to route you have to setup advanced outbound NAT too and some routes. Also the portforward part would be different. However the described setup makes it easy to drop the router in  front of the pfSense later and place the pfSense at the real WAN if this is what you want to do later.

Syncing to head/running head is not supported anyway, so you can do what you want with it as long as you don't ask us to fix it after it broke ;-)