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

Yes, on the download page which links to this: http://wiki.pfsense.com/wikka.php?wakka=WhichVersionIsRightForMe Please take a moment and reread the ENTIRE download page.

We got the donation, and I thank you.  We plan on buynig more drives for the master pfSense server as we are grossly out of space and constantly moving stuff around. Thanks!!!

No.  I would reinstall.

No, this is the method of transferring the location of config.xml.  Not backing it up.  Backing it up is only available via the web interface.

web and mail is only a bunch of single ports. I would use VIPs with portforwarding for port smtp, pop3, http (https, imap, …if neeeded) and advanced outbound NAT on top. Then enable nat reflection at system>advanced and your lan clients will even be able to access your webserver and mailserver by the public IP.

Sounds like freebsd doesn't support that device? Does it appear in the FreeBSD 6.1 hardware compatibility guide?

I have som nexcom 1041c in production, also as CARP cluster. Very nice units. I use both, CF and HDD installs with my units. I summed up some informations how to configure bios and so on for the nexcoms in an earlier mail: http://marc.theaimsgroup.com/?l=pfsense-support&m=113688606829411&w=2 The only thing not so nice when you want to install to hdd is that you have to temporarily mount a ide cdrom to the unit and therefore have to remove the unit from the rack if you want to reinstall it.

Thanks. I should have read the hardware requirements before trying to install it. I'll then get some better hardware and try again.