The fundamental problem that you have have with T1 + DSL is that while you might be able to get routing tables from your T1 vendor, you are very very very unlikely to get them from your DSL provider.
If you had two t1 lines, the classic solution is to get routing tables and to run BGP. However, you can't do that. And so you have to spend a bit of time working on the question. We had a project in corvallis that addressed this issue. The notes from the talk are at: http://www.lug.corvallis.or.us/drupal/node/89 The basic idea is to set a default route based on the measurment of the link status on each side. This is not 100% what you want, and it is not good for load balancing, but it should be possible to keep things going. You can then go into the route table by hand and build which IP -> IP connections you want routed out one number versus the other. It is a mess. It is hard. And it gets little sharp edges that cut and make you bleed. It looks like it is working, until you actually stress it. So what is the "REAL" goal of two networks? Backup pathway? Cheaper routes? Higher reliability? Bob Crandell <[EMAIL PROTECTED]> writes: % Hi, % % I have a client with a T1 and a DSL. I would like to split the traffic % between them. For example, email comes in the DSL and web traffic comes % in the T1. I found it's more complicated than just adding another % default route to the server which has only one NIC. % % I'm open to suggestions. % % Thanks % Bob Crandell % Assured Computing, Inc. % We are hiring. % % _______________________________________________ % EUGLUG mailing list % [email protected] % http://www.euglug.org/mailman/listinfo/euglug ----- John Sechrest . Helping people use . computers and the Internet . more effectively . . Internet: [EMAIL PROTECTED] . . http://www.peak.org/~sechrest _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
