@blak111: Your default allow rule on the LAN interface has the source set to only the LAN subnet. Change it to 192.168.128.0/17 or something that covers all of the networks that route through pfSense. It worked.!! Your my savior!

It was working all along. Tested it with the "pull the plug" techique :)

it's even easier than it looks. I set it up in seconds, of course, not taking into account the slow performance of the webadmin.

any more info what either to configure with 1:1 NAT to get it working correctly? Or if not possible with 1:1, how else to achieve the same result? Thanks!

This will be doable with a single interface on pfSense 2.0, you can have multiple gateways on the same interface, iirc.

I'm having an issue with my multi wan setup here.  When my main internet connection goes down, the router can no longer connect to the DNS servers either gotten from WAN or set in the general settings to forward to the clients.  I believe it still tries to get DNS info through the WAN.  I could set my DHCP server to give the clients a DNS server directly (like openDNS or whatever) But now openDNS will will be asked to resolve names for printers and servers within the network that the router normally takes care of with the "Register DHCP leases in DNS forwarder"  Of course, as far as I've seen, pfsense doesn't even bother looking for the DNS servers on the secondary connection.  How is it that you setup a static route for DNS on the secondary connection and how did you get pfsense to actually use it for DNS forwarding purposes?

well… actually I just have 2 interfaces... LAN & WAN ... @GruensFroeschli: My WAN doesn't directly connect to the Internet, does that mean I have to configure it as a OPTx interface? best regards, -eduardo s.m.

After enabling "Bypass firewall rules for traffic on the same interface" under "system –> advanced" ping to network 192.168.1.x was successful. Case resolved. Thank You GruensFroeschli for a great support and your time. Have a Nice Day!!!

I need to enable a computer to connect to the network with an ip and gateway hardcoded that is out of the subnet set on the nic. I was trying to acomplish this by setting the nic to use multiple subnet, however when I set the subnet of 192.168.0.1/16 I can have any ip in the 192.168.x.x subnet but I  have to use a gateway of 192.168.0.1. If I use lets say 192.168.15.26 with a gateway of 192.168.15.1 it wont work. The main subnet on the nic is 10.0.0.1/24.

Well you have to decide yourself if you really need the LAN interface. You could also put the LAN on a VLAN on vr1 and have the DMZ alone on vr2.

Which documentation did you follow? How do you test? How does it not behave how you expect?

This is called policy based routing. Traffic from the LAN will be handled by the rules on the LAN-tab. You can specify in a firewall rule to which gateway traffic should be sent. However, even if you dont want lodbalancing, you might want to have failover in case one of the WANs goes down. For this you create a normal pool, but chose "failover" instead of "balance". Then select in the firewall rule the failoverpool instead of the gateway directly.

Most of those dyndns services require some sort of client to update their site with your current DHCP'D address.  I didn't see any client with pfsense so where / how does the IP get updated when the provider changes it?  Maybe you could use DNS to create a record to your dynamic assigned address such as mysite.dyndns.org which has your updated Comcast address. Example mydomain.com (Static from Speakeasy)  DNS www IN A <your public="" ip="">www IN A <mysite.dyndns.org>This would allow both ip's to serve your website however, if one fails 50% of the traffic will be sent to the failed one since DNS will round robin the serving of IP's.  Also even if you were to get a service that would update your DNS record when the other failed there is no guarantee that other servers have not cached the static one so they will return the wrong IP anyway.  My advice, if this site is kind of important to your home office or/ business, is to simply get it hosted.  There are some cheap hosting providers out there and your site will probably only go down based on something you did.  Simple google search found http://www.top-10-web-hosting.com/.  For $48 a year its easier than worrying about when your residential service will go down. From your other post you will almost always have access to your site b/c you have redundant outgoing connections.  This is probably the best solution.</mysite.dyndns.org></your>