I see how multiple WANs from different providers (assuming they use different link-level sources and/or technology) can provide backup for outgoing access, but I haven't figured out how this can help for incoming access to servers.
I.E., let's say I have 2 WAN connections with public IPs; 98.76.54.231 via a cable-based ISP and 123.45.67.89 via DSL-based ISP. Now say I run a web server, www.mydomain.com, that has a DNS-resolvable public IP address of 123.45.67.89 (i.e., the DSL-based WAN). If my DSL-based WAN goes down and pfSense nicely re-routes everything through the cabled-based WAN, how does one (re)route the traffic coming into www.mydomain.com to target the cable-based WAN at 98.76.54.231? The only way I can see of doing this would be to have a DNS server that provides fail-over but, given that DNS servers are highly distributed and employ timed caching, such a fail-over would take considerable time to propagate (likely more time than the typical ISP's outage, or so one would hope?). Is there something I'm missing, here? FYI, for us this is a real problem that I'd like to solve. ______________________________________________________________________ Previous message from Chris Buechler on 2008-03-06 at 4:11 PM -0500 ---------------------------------------------------------------------- |Anil Garg wrote: |> Now that the broadband is very reliable, why would anyone use more |> than one WAN at home. What are the benefits you have seen or desired |> in multiple dhcp wan at home. | |"Very reliable" depends on your provider, your definition of reliable, |and even more, your tolerance for downtime. My tolerance for downtime is |0. I work a significant amount out of my home office, largely on |servers, routers, firewalls, switches, etc. in remote locations where I |must have an Internet connection. My primary 15 Mb cable connection is |down around 4 hours a month on average, and once a year or so for 48+ |hours straight or longer. | |While that's no big deal for your typical residence, it's critical for |me and *always* happens to me at the worst times. When you have clients |that rely on you being accessible to assist any time, the money spent on |the backup DSL connection is well worth it and a relatively |insignificant cost. When I'm doing something critical after hours, I |don't want to be stuck driving into the office or elsewhere with a |working Internet connection at 3 AM to finish the job. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
