<br><font size=2 face="sans-serif">The same thing could have been acheived with a weighted DNS entry or round robin DNS no?</font>
<br>
<br>
<br>
<br>
<br><font size=2 face="Courier New"> The scenario here is more of switching ISPs.<br>
<br>
Commonly, you would have two different routers, one from each T1<br>
provider, and you may not have direct access to their configuration.<br>
If<br>
I understand the setup correctly, each T1 router was connected to a<br>
separate NIC on the server. This iproute2 method allows you to use<br>
both<br>
WAN connections "separately". It is not really a high-availability<br>
or<br>
load-balancing thing, it's merely a way to transition from one<br>
provider<br>
to another.<br>
<br>
--Jeremy<br>
<br>
I understand the intention here and that is the point I was trying to make.<br>
Even if you're working with disparate ISP's, you can mux the connections<br>
into one pipe for transition purposes so you don't get dumped traffic<br>
inbound since it's sees one origination interface. The bit about bandwidth<br>
and filtering was just so you could monitor what comes and goes on each<br>
individual pipe. <br>
<br>
Matt</font>
<br>
<br>