This limitation should no longer be present in the pfSense 2.0 beta snapshots. Give them a try.

@Cry: Presumably it's specific to your ISP since it if was specific to pfSense this forum would have been flooded with other posts (and I wouldn't have been online for a long time). Could well be - I use Time Warner cable with a dynamic IP. At work I have Time Warner with a static IP and have had no issue. The cron job seems to have fixed the problem for me and others. I'd be glad to provide more details to anyone interested in looking into/correcting the issue.

I suspect you'll need 4 - 3 for WAN and one for LAN. VIPs is what you're looking for regarding multiple WAN IP addresses.

4 mbp/s connection? Tell them to tether their phone on 4g, or even 3g.

You can script that with wget. Some searching here will find scripts and other examples.

subnetmask.info is a useful site, you tell it how many nodes you need and the base network and it will tell you what subnet mask and other stuff you need.

My previously asked questions in this thread are just as relevant to your configuration.

You're blocking bogons on your WAN interface which is populated by a file which is regularly updated.  pfSense downloads this file regularly.  That's what you're seeing in the logs.

There isn't any such build at this time. May be in the future, probably with FusionPBX rather than our Freeswitch package (the creator of which, mcrane, went on to create FusionPBX). There are a lot of people using the Freeswitch package though. Just not an appliance build specifically for it.

@torontob: 1- I want to know how the backup can be triggered? Would OS boot automatically fall to the second partition if the first fails? 2- Would it be by simply choosing option 2 at boot time? 3- What is the way to set the mirror as the default at start-up? 4- Are the configurations copied between the two mirrors as a system is built? If not, really this other partition is useless and waste of space isn't it? Since, it's probably much more cleaner and might take the same time to re-image the whole thing anyhow. you have to choose it at boot time. yes Diag>Nanobsd there is one shared config partition. It's primarily if you want to upgrade one and have the option to revert back to the previous version. (with caveats for drastically different versions, like 1.2.3 vs. 2.0, where the configs aren't compatible)

Just remove it. Without the % it logs to just normal plain text files. Be aware, you will have to monitor the logs and either rotate them manually or setup an automated process.

First hit on pfSense irc on Google, also found one click off of the pfSense home page.

You may need multiple overrides for variations of the domain. ( like example.com and www.example.com )

Virtual IPs are exactly what you want to use.  Consider implementing 1:1 NAT for your servers which means the virtual IP addresses will live on the WAN interface of your pfSense box and each unique IP will be NAT'd to the specific server you want to give access to.  Depending on the security stance of your network, it would be a good idea to consider putting your Internet facing devices in your OPT1 network and implementing firewall rules to limit their access into your LAN.

It would be better to assign your second static IP as a VIP on WAN, and then use 1:1 NAT to associate it with your internal server. If you only had that server on a segment, you could bridge it to WAN and assign it directly, but that isn't advisable (or workable) if you have other items on LAN that are privately numbered which need NAT applied.

Unless you are assigning those DNS servers directly to clients in those subnets with DHCP, it can't be done in that way. The DNS forwarder can't pick and choose which upstream server to use for clients in that way.