Re: multihomed linux box

2001-07-11 Thread aphro
sorry bout the long delay my mail server decided to die on me a couple days ago..copy/pasted your reply from the archives. GNU Zebra :) i'll check that out. Oh, and I have good news: in my *limited* testing, your trick with the metrics works fine: I remotely disabled one of the internet connec

Re: multihomed linux box

2001-07-10 Thread Phil Brutsche
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... > > > Generally BGP is the way to do it. > > BGP is outta the question for me..i asked cisco about that a couple > months ago and they said 128MB was minimum for BGP on routers. And that's no

Re: multihomed linux box - dual t1

2001-07-09 Thread Phil Brutsche
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... > how does that work though? the rest of the world has to know how to > route to you..without that information i cant imagine a thing in the > world you can do on a server to advertise you :)

Re: multihomed linux box - dual t1

2001-07-09 Thread aphro
> -BEGIN PGP SIGNED MESSAGE- > No workarounds. Policy routing :) how does that work though? the rest of the world has to know how to route to you..without that information i cant imagine a thing in the world you can do on a server to advertise you :) i can't believe this is such a diff

Re: multihomed linux box - dual t1

2001-07-09 Thread aphro
> > hi ya... > > think theres lot's of folks with dual t1... > > for outgoing traffic... think the routing and metrics might work.. yeah all im concerned about is outgoing traffic. > for incoming traffic... we'd need all kidns of whacky work arounds >or an autonmous ip# routable by either

Re: multihomed linux box

2001-07-09 Thread aphro
> > hi ya aphro/phil > > this same almost exact same concept just went thru the firewall > mailing list > - same conclusions... > > their ideas is to let the routers do the NATing > and "Load balance the external routes using EIGRP or OSPF" yeah my routers do NAT already. and i do

Re: multihomed linux box

2001-07-09 Thread aphro
> Generally BGP is the way to do it. BGP is outta the question for me..i asked cisco about that a couple months ago and they said 128MB was minimum for BGP on routers..my routers have 8MB each .. > I think it can but only if your routers send out RIP packets :) If > they don't, can't, or whate

Re: multihomed linux box - dual t1

2001-07-09 Thread Phil Brutsche
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... > > hi ya... > > think theres lot's of folks with dual t1... Or dual DSL, or DSL + Cable modem, or dual DSL + Cable modem (like I have at work). > for outgoing traffic... think the routing a

Re: multihomed linux box - dual t1

2001-07-09 Thread Alvin Oga
hi ya... think theres lot's of folks with dual t1... for outgoing traffic... think the routing and metrics might work.. for incoming traffic... we'd need all kidns of whacky work arounds or an autonmous ip# routable by either isp... - who's writing this howto ??? -- UUnet also has a backup

Re: multihomed linux box

2001-07-09 Thread Alvin Oga
hi ya aphro/phil this same almost exact same concept just went thru the firewall mailing list - same conclusions... their ideas is to let the routers do the NATing and "Load balance the external routes using EIGRP or OSPF" search the firewall archives for: http://lists.gna

Re: multihomed linux box

2001-07-09 Thread Phil Brutsche
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... > hi. > > i have this setup on 2 machines > > > Machine A > \ eth0 ---> Switch --> Router A(65.xxx.xx.x.x) --> Internet > \ eth1 --> Switch --> Router B (63.xx.x.x.x.x) --> Internet > > Machin

multihomed linux box

2001-07-09 Thread aphro
hi. i have this setup on 2 machines Machine A \ eth0 ---> Switch --> Router A(65.xxx.xx.x.x) --> Internet \ eth1 --> Switch --> Router B (63.xx.x.x.x.x) --> Internet Machine B \ eth0 --> Switch --> Router A (65.xx.x.x.x.x) --> internet \ eth1 --> Switch --> Router B (63.xx.x.x.x) --> internet