[lug] Linux as a router for 2 DSL lines.

[Brad Doctor]

One option that may work is to use IPtables via kernel 2.4.x.  Here is a 
potential set up:

NIC-1 has 10.1.100.x (DSL1)
NIC-2 has 10.2.100.x (DSL2)
NIC-3 has 192.168.0.x (Internal)

With IPtables, it is possible to use a pool of addresses for outbound 
connections, in conjunction with SNAT, and specify what ranges you wish to 
use (one or the other of the NIC-[1,2] addresses).  Since each device has 
it's own route to it's own DSL modem, this may work.

Actually, if memory serves, I believe you can force the Cisco 675 devices 
to not do DHCP on the internal side, and configure what network they are to 
use, so indeed, I think this would work :)

What this will then do is switch what IP is used for every unique TCP/IP 
session, and it works incredibly well.  Outbound load balancing, essentially.

http://netfilter.kernelnotes.org is the home for IPtables, although it is 
down for me at the moment (unrelated to anything mentioned here, heh).

Have fun!
-brad

At 07:29 PM 5/4/2001 -0600, Jason Vallery wrote:
>I was just sitting around talking with my neighbor that a share a duplex 
>with and we were discussing the possibilities of sharing our bandwidth. We 
>both have DSL from qwest coming into our homes, both using qwest.net as 
>our ISP. We both have the external Cisco 675 modem. What are the chances 
>of setting up a Red Hat machine to act as a router for our home networks 
>so that we can share both DSL lines? My original thought was an approach 
>similar to "shotgunning" an analog modem. Setting up the redhat machine 
>with 3 NICs. One to each DSL modem and the third to our home networks then 
>using a DHCP server on the redhat machine to assign IPs to the internal 
>network and to route the traffic. The way the 675 works with qwest.net is 
>that it acts as a DHCP server and assigns a 10.0.0.X address to anyone on 
>its network requesting one, and then it gets a routable 60.*.*.* IP from 
>qwest's DHCP server. Unfortunately I am not familiar with IP chains and 
>port forwarding (Which is what I imagine it would take to accomplish 
>this). So does anybody have any suggestions on how this could be pulled off?
>
>Thanks
>
>Jason Vallery
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20010504/f95425c7/attachment.html>