<div>Hi all,</div>
<div>I have managed to setup a Fedora 7 box with 3 ethernet cards and two ADSL modem/routers from different suppliers as LARTC recommends. I am able to direct traffic for specific internal IPs either to one or the other ADSL line. However, I am faced with two problems I am struggling for the solution:
</div>
<div> </div>
<div>1. I have opened a few ports on the ADSL router/firewalls to talk to internal hosts; say when someone hits <a href="http://myADSL1_IP">http://myADSL1_IP</a> I would redirect him to <a href="http://192.168.0.10">192.168.0.10
</a>; while if someone hits <a href="http://myADSL2_IP">http://myADSL2_IP</a> I would redirect him to <a href="http://192.168.0.20">192.168.0.20</a>. If I have rules such as the following all works well:</div>
<div> ip rule add from <a href="http://192.168.0.10">192.168.0.10</a> table ADSL1_rules</div>
<div> ip rule add from <a href="http://192.168.0.20">192.168.0.20</a> table ADSL2_rules</div>
<div>Unfortunately, if I want to do the reverse it does not work. I can't have a host prefer one ADSL line, but still receive traffic from the other ADSL line. It may sound weird, but I only want to have one host reply to any of the two IPs, either from ISP1 or ISP2. With the current configuration I can't. It works ok the default ISP of the host, but can't make it to work for the other.
</div>
<div> </div>
<div>2. I tried using </div>
<div>ip route add equalize default scope global nexthop via myADSL1_IP dev eth2 weight 1 nexthop via myADSL2_IP dev eth1 weight 1</div>
<div>It doesn't seem to perform round robin for every request, more like it caches the route to use per host. Is it possible to force a real round robin or (better) weighted routing without resorting to a new kernel - as suggested in the article? I think I've seen recent threads saying that it is no longer necessary to create a new kernel.
</div>
<div> </div>
<div>Thank you in advance for your help</div>
<div> </div>
<div>Kostas<br>-- <br> </div>