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 ;-)

Installing via netboot is under developement. In the meantime just install the hdd in another system from cdrom and move it over to the "funny" box after that.

I understand what your needs are, but it's not too easy to maintain a complete collection of installs for differnet type of systems. We only offer support for 2 types of systems, embeddeds (aimed at sbc but will run on more powerful machines too but yet should work with low end hardware) and full installs (the main target platform of pfSense). I doubt that tere will be some change of this philosophy in the near future. It's already hard enough to improve and test pfsense for these 2 platforms.

Besides that traffic shaping won't work in bridge mode it is doable. Bridge LAN to WAN and enable filtering bridge at system>advanced. We have a nice tutorial online that describes just what you want to do: http://pfsense.com/mirror.php?section=tutorials/transparent_firewall/transparent_firewall.pdf

should work fine we setup a lan on a vlanof (sis0) for management and the bridge the ath with the sis interface.

i am also running it on a Nokia ip330.  all was fine until yesterday when i tried to update it to the latest version.  it boots but then i can't get to it.
you don't need to reflash it, i have always updated with the firmware upgrade feature.

i am not sure if the nokia can handle the 512 ram.  i think the max is 256?

Packages are NOT SUPPORTED on embedded at all.

Last I heard NTOP was working.  Be sure to visit NTOP settings before trying to access the service.

Left the config.xml file at work. Will send it to you on Monday. BTW I managed to restore it on a fresh RC1a install but it keeps failing on the Releng1 CF image install.

Also experienced some problems with the Releng1 Image. It hanged after trying some OpenVPN connection, it only answered ping during boot up but when it finished to boot only the serial console was working and I couldn't reach any of the interfaces but they gave DHCP leases.

Maybe its a problem with the 12-07-2006 REleng1 snapshot Image.

Will try to repeat the OpenVPN configuration on Monday and see if it fails with the RC1a image.

Thanks