The best solution would be several cards trunked into the switch with the appropriate number of VLANS configured. Fast, flexible and convenient. But, it seems that this is impossible on pfSense as of yet. A hack is to bridge individual VLANs on each interface, but I continually run into problems trying to implement that. When you add two pfSense machines and CARP, that brick wall suddenly appears just in front of you. A single card with multiple VLANs works perfectly.

Please first get a basic grasp of how routing works and what a routing table is. A good place to start is: http://en.wikipedia.org/wiki/Routing http://en.wikipedia.org/wiki/Routing_table Try modifyng the routing table of one pfSense via "System –> Static routes" and observe the changes under "Diagnostic --> Routes".

The multiwan docs are not at all clear for simple failover I'm working on it. As far as I understand it, this is correct.  I would imagine I could even make do with a single pool, right? Correct Additionally, is there anything to be touched in the NAT section? Nope I also have inbound rules, but I'm not very concerned with duplicating those on the ADSL circuit.  Is there anything to alter for inbound rules and nat? Nope CVfailstoBWAY    gateway  (failover)    opt1 wan 216.220.96.17+67.83.242.65 Bway preferred when CV fails I prefer wan opt1 (different from the docs) are those IP address your dns servers? if not you'll need static routes for each DNS server.    

Please share your experience after testing, good luck!

This is kind of a hack but it works: Create a loadbalancing-pool with only one entry: your WAN. Download the config.xml, find the loadbalancing-part and replace the WAN-part with your other gateway. Restore the modified config.xml. Now if you use in a firewall-rule as gateway this balancing-pool, traffic handled by this rule will be directed to your second gateway.

The only problem with changing IP addresses on clients is that it tends to cause some temporary confusion on the network, particularly with Windows file shares. This made me think of some old bat files :) netsh interface ip set address LAN-connection static 192.168.1.110 255.255.255.0 192.168.1.1 integer netsh interface ip set dns LAN-connection static 192.168.1.1 @echo off echo Enter username color 01 set /P Username= echo Enter Password set /p Password= cls color 08 net use Z: \\192.168.1.200\data %Password% /user:%Username% net use i: \\192.168.1.200\install

I would make WAN1 your cable, WAN2 your dsl. Then under Static Route, have only 1 route created in here. Select WAN2, ip of the device you are pinging for load balance, gateway of wan2. The above will ensure your load balancer checks will use the proper interfaces. After you do that follow this tutorial http://doc.pfsense.org/index.php/MultiWanVersion1.2.

Ahh good idea. Though I do not want to put another device in front of the pfsense box, that gave me an idea. My speedstreams have the option to give public or a private IP, I can just enabled private IP on one device and should be good to go. Thank you!

Thanks so much for your reply - I will continue with a separate server for proxy Manjula

is that script worked?

Thanks, the solution presented in your thread looks like the best solution. I am going to try it!

For multicasts to go over the router, the router has to be multicast-aware. You could try a 2.0_alpha build since ermal added an igmpproxy daemon. http://forum.pfsense.org/index.php/topic,13312.msg71539.html#msg71539

Solved. I was using policy based routing in my firewall rules. I just had to add a manual rule to the destination network and make sure that the default routing table was selected

static port did nothing, just worked out im running 1.2 will look at going to 1.2.2 or 2.0 (1.3) just do i have enuff bits to set up a new system and keep the old one as a fall back if need be. The Pain lol.

Great! ;D At the very least I'd recommend you remove that gateway entry for the OPT1 interface though. As far as I understand your configuration there is no Internet gateway available at 98.175.61.225 (that's what your pfSense box is for!). You should only ever fill that box on interfaces that face the Internet.