Lawrence Horvath wrote: > On 6/22/06, L. V. Lammert <[EMAIL PROTECTED]> wrote: >> At 11:13 PM 6/21/2006 -0700, Lawrence Horvath wrote: ... >> Keep in mind also that redundancy is fine for outgoing traffic, but >> to actually route incoming traffic you must also have an upstream >> ISP(s) that can handle redundant links, or you will have to obtain >> your own ASN and manage your own BGP. >> >> Lee >> >> > > there are only two ways i know to maintain routing on incomming > traffic, first being to have your DSL and T1 from the same company and > they can set up your links with routing on there side that will > reflect your fail over situation, the second way is to multihome with > and AS and run BGP, ...
There are also DNS games. Multiple MX records, multiple nameservers in the different ISP's IP space, DNS load balancing for http[s] (e.g. 'nslookup www.yahoo.com')... These work suffuciently well for applications that understand multiple Ips for a given name, or applications that understand the concept of "if IP address A times-out, try IP address B." OpenVPN understands this, for example. -Steve S.
