Here is the marketing text from Clavster, entry level is $980, is this on the development list?? WAN Load Balancing, or Route Load Balancing, is an important function for most companies regardless of application. It enables you to connect multiple Internet Service Providers (ISPs) to your Clavister product to ensure optimal Internet access, even in the case when one ISP service fails. By utilizing both Internet links at the same time, you can route outgoing traffic to the link with the most free capacity and/or with the lowest latency. By combining WAN Load Balancing with our Host Monitoring functionality you can make sure that the traffic distribution is dynamic and based on the current capacity and quality of each link. The WAN Load Balancing functionality is a must for any organization that require high quality Internet access at all time without having to pay for extremely expensive lease lines.

anyone?

While it is best to avoid such overlaps, more specific routes do get considered first as SeventhSon mentioned. It should work fine.

Would love to see a network diagram of this to get a better visual of what your trying to do. www.gliffy.com

Create an 1:1 nat on firewall -> nat -> 1:1 with your WANX (one that nobody is using) and your ubuntu ip address, this will enable all traffic to, from, your server.

If WAN1 is dedicated to your IP phone, why don't you use 1:1 nat?

I don't get it, probably it's because your nating.

Alright, thank you guys!

It'll Pass all the traffic to alive gateway in case of any one wan fail-over!

only way for that to show up like that is if it's destined to the MAC of the firewall, or broadcast. The latter is highly unlikely. Seems likely the 192.168.10.111 device has a wrong subnet mask on it so it's trying to send that traffic via the firewall, not recognizing 192.168.8 as local.

@edwin1188: buenos días, también presentamos el mismo problema y no sabemos como resolver o si hay que configurar algo adicional. Buonos dias, tenta aqui: http://forum.pfsense.org/index.php/topic,49702.msg265524.html#msg265524

We have looked into that before but had issues with it. We may revisit it again once we're on FreeBSD 10.

Nothing obvious there - except I need to update my own ESXi  ::) Is the LOM the only NIC?  It's a bit unusual using that with anything but management. Do you happen to have both tagged and untagged VLANs on the same interface. Good luck with the Netgear site.  I've been there before.  Had to try three different browsers before I got one that worked.

Hey ImageJPEG Like gderf said, you cannot have two gateways with the same IP. Instead what you want to do is assign unique gateways, even if you want them as seperate LANS, you can do this later by simply assigning a firewall rule to block any outgoing and incoming connections with the two. Just a questions, are you using internal IPs are examples or are you trying to setup LANs? If you are trying to setup LANs you can use LAN1 - 192.168.1.1 LAN2 - 192.168.2.1 As far as WANs you can use whatever information your ISP gave you, usually in your CIDR. Gerardo

Hi skygizmo What are you trying to accomplish? If it is redundancy, having to Comcast connections probably wont give you what you are looking for. If it is bandwidth + ip block, i would look at the business plans tiers (pricing and such) and see if it cost effective instead of two different packages. If you then are trying split a home network and business network, that can be accomplished with pfsense and a managed switch.