@gregoryc911: @kc8apf: You add them as virtual IPs under Firewall/Virtual IPs.  They can then be used for 1:1 NAT, manual outbound NAT, or port forwarding. So should I leave the WAN as DHCP?  Right now for testing I have the WAN set for the .240  If it is supposed to be DHCP I will change that and make the setting changes. Thank you again in advance! ;D The WAN interface would generally occupy one of the static IPs.  All the other static IPs would be added as virtual IPs on the WAN interface.  You could run DHCP on the WAN interface and have all the static IPs as virtual, but there isn't any benefit unless you needed all your static IPs for some special purpose and used the DHCP address for outbound NAT or something.

You just described why FTP and voip are such problematic protocols…. It is usually solved by forcing these protocols to only one WAN and not balance them. The other possibility is to use sticky connections. Use sticky connections Successive connections will be redirected to the servers in a round-robin manner with connections from the same source being sent to the same web server. This "sticky connection" will exist as long as there are states that refer to this connection. Once the states expire, so will the sticky connection. Further connections from that host will be redirected to the next web server in the round robin. however i dont know what the status of that feature is. The last i know is, that it doesn't work like it should.

If I recall correctly, you can edit the config file (viconfig from console or backup/edit/restore) and add two more additional dns server tags that aren't accessible via the gui in 1.2.x.

OK, understood on the rules for WAN interfaces, use default. Any explanation (or theory) then on why (at least it seems to me) the port forwards do not work then when using the failover pool gateway for LAN_VOIP->WAN and using the default gateway for WAN2->LAN_VOIP? When configured like that, VOIP calls are dropped after a minute. I am a little stumped on why the calls are dropping. Thanks!

I cant code myself  :-\ In my limited knowledge, you would use PHP as the scripting language, I would guess you would also need to view the source of the portal page you need to authenticate against and look for any references to <form>with attributes for username & password etc, you would then use this information in your custom.php file to submit the required data. look here for how you can use PHP functions http://www.w3schools.com/php/php_post.asp If you think thats way over your head then I would suggest you contact a developer with a bounty as this is a pfsense customisation or just post the request in the bounty section of the forum. Bear in mind, that your wireless provider might employ timeouts, in which case your opt2 will be marked/shown as being offline in your multi wan envoirment. Hope that helps Slam </form>

FYI- I opened a feature request ticket for this: http://redmine.pfsense.org/issues/show/290

Thanks for your swift reply! :)

PPPOE sessions with 2.0 bring nothing really when they on the same Gateway. So you will still have to use hardware or virtual routers. If you want to use PPPOE sessions on the same gateway. You should get ClearOS. They support this. With PFsense any version, you will still need to run minimum of 2 hardware routers or 2 virtual ones on the server computer or behind it.

Forget it. Go get ClearOS 5.1 once known as ClarkConnect. It can do all that with just one VM. It can work with several PPPOE connections without the need to setup virtual gateways. You can install it wout any optional services at all so its much easier on the computer. So it consumes less memory and less everything. Pretty easy out of the box. Not worth bothering with pfsense if it doesnt work out of the box.

Well I can say is that the WAN setting on my time to say that the link is down, but the funny fact is that reversed the links last week, did a fresh install with the links inverted, and the errors in the wan still, if a developer wants to connect and make a verified, I will be available.

@rudraansh: Instead of creating more and more rules. Use Smoothwall as a content filter on different machine and use Advance Proxy abd URL Filter plugin, It will solve all your content filtering related issues. Until Pfsense doesnt work perfectly u can use that. I think pfsense works perfectly with me, but the problem is creating rules im not an expert on that.  But do you think the rules are correct? And thank you for the quick reply.

system –> static routes Click the +, select the interface over which the destination is reachable, set the IP you want to point to the gateway with as subnet /32, set the gateway of the WAN you want it to send to How to add static routes is described in various places (i myself wrote it countless times here in the forum...)

I worked around something like that: I did it by having an OpenVPN connection between the two locations. I then forwarded the traffic to an IP on the other side of the tunnel. For traffic leaving back the original way i enable AoN and NATed traffic into the tunnel. Like this all requests seem to the server as if they come from the pfSense on the other side of the tunnel.

You should set your pfSense into bridging mode. Get rid of the VIPs. Don't assign a public IP to the WAN or LAN of the pfSense.   Just set a private IP so you can manage it. After bridging LAN to WAN, make sure your servers have as default gateway the router 50.40.30.1/24 (the router in front of the pfSense). Create rules on the pfSense allowing traffic from the WAN to your server and from your servers to the internet (if they need internet access).