Hi Philip, That's simply brilliant. However, as you said, it would introduce another single point of failure. Further, to be honest, I sometimes tend to get flummoxed. Therefore, a simple solution might be a better fit.
I'd gladly settle for something that's not-so-clean... but is simple to maintain in the long term. In other words, it would be OK to drop an occasional call as long as we recover in a few minutes time. Thanks for the elegant solution. Dan On 9/22/2010 7:08 PM, Philip Prindeville wrote: > About the only really cleanly working solution I can think of is to have a > "proxy" in a data center that accepts traffic for address 'A', and then > encapsulates it (either via IPsec ESP with NULL encryption or with GRE) and > then forwards the traffic to your IP addresses B and C. > > You can decide what policy you want for that: easiest is all traffic to B as > long as the tunnel is up, and then failing over to C when the tunnel goes > down... > > That, on the other hand, introduces another point of failure, and requires > you to potentially renumber your network to expose 'A' as your address > (whereas previously 'B' or 'C' might have been your published address). > > > On 9/22/10 3:12 PM, Dan Ryson wrote: >> Thanks Philip. >> >> Regardless of what it should be called, what we need is fail-over >> diversity. For our purposes, we hope to avoid having two circuits from >> the same provider because when our cable modem stops working, cable >> Internet service also quits working at neighboring businesses in our >> complex. We've found the same to be true for our DSL line. However, >> they've never (knock wood) failed at the same time. >> >> Dan >> >> On 9/22/2010 3:42 PM, Philip Prindeville wrote: >>> Technically, "multi-homed" is exactly that: having more than one IP >>> address. >>> >>> Doing hot-failover with no loss of connectivity is a lot easier to do with >>> two circuits of the same kind (or at least through the same provider, >>> terminating into the same peering gateway). >>> >>> >>> On 9/22/10 8:16 AM, James Babiak wrote: >>>> Dan, >>>> >>>> You're not really 'multi-homed', you just have two Internet circuits. If >>>> one goes down, it's not like you can use the same IP address on the >>>> other one. >>>> >>>> What you can do though is setup the second circuit as a fail-over if the >>>> first one goes down. We do this and it works very well. We basically >>>> have a script running in the background that monitors for connectivity >>>> on the primary circuit. If it loses connectivity for so many seconds, it >>>> will test to see if the secondary circuit is online. If it is, it >>>> changes the default route to use the secondary. It continually monitors, >>>> using a host route, to see if the primary circuit comes back, and if so >>>> it changes the default route back over to it. >>>> >>>> Keep in mind that any external calls in progress when the primary goes >>>> down would die. >>>> >>>> -James >>>> >>>> On 09/22/2010 10:42 AM, Dan Ryson wrote: >>>>> I think this topic has already been discussed before on this list. >>>>> However, Google and I can't seem to find the discussion thread. >>>>> >>>>> We have fixed IPs from both a cable and DSL provider. It it feasible to >>>>> our multi-home AstLinux using a Soekris net5501? If so, how? >>>>> >>>>> Thanks. >>>>> >>>>> Dan >>>>> >>>>> > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
