Hey, Got a work around in the end. I turned the firewall and everything back to normal so the captive portal worked. I then setup a Virtual IP for my whole WAN range and then added a NAT 1:1 rule for each IP address. Since this cant include the WAN IP address I couldnt just do a /24 range. I therefore setup NAT 1:1 for a /25, /26, /27, /28, /29 and a /30 range so that I covered 192.168.0.4-255. Now if a PC on my LAN network with a IP address of 192.168.1.123 uses the internet the traffic appears to come from 192.168.0.123. There was probably a better way to do this but it worked for me.

GruensFroeschli can you help me with image upload ? im newbie  :'(  :'(  :'(  :'(

@ktims: Have you read the MultiWan documentation? This is a very straightforward setup and you should be fine using the basic setup. Yes.. I read but i am unable to setup.. please can you send me the some documentaion or can you brief me how to setup please

Yeah, I always make three- load-balance both lines, failover from WAN to OPT, failover from OPT to WAN. Just to be flexible. You want to use the failover pools and not an interface gateway so you don't break https (or whatever) when a line drops.

I've been downloading a backup config with the GUI.  I then use a text editor to search and replace the monitor IP I want to change…then I upload the "fixed" config.  It would be nice to be able to edit this value without having to reconstruct the pool.

My guess would be that you miss configured the static routes screwing up the DNS requests, maybe you got the CIDR wrong (/32) [image: Untitled.png] [image: Untitled.png_thumb]

Will each NIC be connected to a separate modem, or are all of the WAN connections going out through the same cat5 line (like the internet accounts at my apartment building)?

sorry it took me so long to respond, but if I plug in my laptop into the router, it gets internet access fine. It's only the pfsense that can't ping out. The pfsense box can ping out as far as the cable modem. It pings the router and cable modem fine, but I try to ping the cable modem's gateway and it just doesnt get anything back.

Yes you can surely do that.

The gateway should be the load balancing pool for the client.

Yes you can do it.

Squid Guard , Squid doesnt work fine when used in a MultiWan Setup. I have faced the same issue and Now I am using a very old harddware of mine which run behind pfsense and i have installed smoothwall in it which does the rest of the content filtering. and when you say that your customer is facaing the problem you can always use smoothwall in an additional machine saying that if there is a hardware failover on the pfsense side. you just need to plug the cabl in smoothwall and you will save a lot of downtime.

For the below rules .remove the below two rules. Just have the one above . And sunny is right , put Open DNS servers as your monitor IP instead of using your ISP Servers. in place of DNS  also you can use the same Open DNS servers. and check I think this will resolve your issue.

Change the pingable ip of all the ISP to an OpenDNS Server. Lke 4.2.2.2 or 4.2.2.4. ITs better to keep an ISP's IP.But as you are facing these issues .Its better try these. One more thing, do you have a router from ur ISP. If that is the case then your pingable IP may be of the router, which is set next to pfsense and after router there is no connectivity. Check that.

Please show screenshots of the rules that dont work.

WAN: Destination "WAN address" means exactly that. You allow access with your first two rules to the IP of the pfSense. Nothing more. If you want to allow access from the first two subnets to the LAN on the pfSense you have to set as destination: "LAN net" Also dont forget to set on the vyatta side a static route for the 172.16.15.x/24 subnet pointing to 172.16.5.5. What are your rules 3 and 4 for? LAN: Basically delete your first 4 rules. They dont do anything. The last rule you have allows everything in your LAN to the WAN. You also need to make sure you have a static route on the pfSense for the 172.16.3.x/24 pointing to 172.16.5.10.