hi ya
> On Mon, 9 Jul 2001 [EMAIL PROTECTED] wrote:
> >
> > The issue, I think, is that the poster DOESN'T have an autonomous
> > or portable address. So in this latter arrangement, while he can
> > play all sorts of router tricks about which provider a given outbound
> > packet gets sent to ("shouldn't" matter, since both providers peer
> > with the rest of the Internet), *inbound* traffic only ever comes
> > over one link, and when that's down, he's dead.
> >
>
>
> A solution I use at home (dsl + modem backup, two different providers) is
> this.
>
>
> ##########
> |--dsl-----##########
> me-| #internet#----work
> |--dialup--##########
> ##########
>
> I establish a tunnel to work over the dsl. If the dsl goes down, the
> tunnel reconnects via the dialup. I keep the same ip address(es) for
> incoming traffic and my home mail server doesn't go down, no fancy routing
> involved.
i think this is the norm... but it works ??? because...
a) you have ppp + tcp/ip
b) you either use one or the other...but NOT both at the same time
c) you dont have www.you.com where the folks on internet needs to find
your server on your dsl line ...
for the dual T1 case.... it wont work for many reasons ??
a) both are tcp/ip
b) we want to use both t1 connections and load balance um
c) we want the outside world to always find our www.foo.com servers
which requires an autonomous ip# routable by both ISPs
and/or tricks play locally
or the NATing scheme present earlier... but several
knowledgeable experts
i am thinking of more tricks ??? .. just thinking outloud...
isp#1 routes 1.2.3.4 to www.foo.com
isp#2 routes 5.6.7.8 to www.bar.com
and the end result you want to display is actually www.result.com
you do your local virtual hosting to map foo.com to result.com
and bar.com to result.com
( foo.com and bar.com are both virtual domains on www.result.com
( server
c ya
alvin
_______________________________________________
Firewalls mailing list
[EMAIL PROTECTED]
http://lists.gnac.net/mailman/listinfo/firewalls
