Multiple DSL connections on single network

Jul 8, 2018
1
0
10
I have inherited a network from a colleague I used to work with, we suffer with very poor DSL speeds (2 down, 0.5 up as an average) and need to handle compressed video, multiple audio feeds (sometimes six/seven incoming audio connections, no outgoing) and some light FTP and other light data traffic. Too much for a single connection and all other methods to improve with it have failed. The way my colleague dealt with it before is to create six separate networks, six DSL routers, six IP bases and the like for each purpose (video is on x.x.3.x, audio on x.x.2.x, FTP on x.x.5.x, data on x.x.4.x etc). The issue there is that nothing can talk across the networks due to the IP addresses and subnet masks restricting access to only that one network, you then have to change IP address to gain access to another service and to me that does not feel right.

Device wise there is no more than 255 devices so it could all sit on one IP range easily, I just can't figure out in my head how to then deal with that practically - would you just specify the default gateway in some devices that needed to talk to the internet (some devices don't and are internal only) as the suitable router for that purpose? So say devices 192.168.1.10 - 192.168.1.20 could have the default gateway of 192.168.1.9 and then the next batch of ten have another default gateway (such as .1.8)? From my understanding the default gateway is how you get out of the subnet mask range (correct?) so for the devices in the .10 to .20 range then for them to get outside of the 255 address mask they call to the gateway?

Thanks for any ideas - this feels as though it should be simple but I am struggling to figure out a practical solution to it

 
Solution
Although it will be very messy you can use them all on the same network.

You would assign the router for example 192.168.0.1-192.168.0.6. One "and only 1" of the routers can run DHCP to assign ip addresses to the end device. It would assign them say from 192.168.0.100-192.168.0.200.

The hard and nasty part is how you make all this work. Of course it is pretty easy to just use the ROUTE DELETE and ROUTE ADD command to just change the 0.0.0.0 gateway. Make it work by application is much much harder. You should be able to get it work with route add statements for particularly sites on the internet.

Maybe better off contacting the ISP and see what they offer. If they offer it they can bind DSL connections with special modems...
Although it will be very messy you can use them all on the same network.

You would assign the router for example 192.168.0.1-192.168.0.6. One "and only 1" of the routers can run DHCP to assign ip addresses to the end device. It would assign them say from 192.168.0.100-192.168.0.200.

The hard and nasty part is how you make all this work. Of course it is pretty easy to just use the ROUTE DELETE and ROUTE ADD command to just change the 0.0.0.0 gateway. Make it work by application is much much harder. You should be able to get it work with route add statements for particularly sites on the internet.

Maybe better off contacting the ISP and see what they offer. If they offer it they can bind DSL connections with special modems. Many do not want to deal with this. VDSL is one example of a very common bonding offered by many ISP.
 
Solution
To get multiple PCs on separate subnets to communicate you need VLANs. Each VLAN could have it's own connection.

A load balancing router can manage connections on each gateway. I'm not sure how well this will work since video streams might eat up an entire one.

I agree with bill that trying to get the isp to bond it for you is the best way. multiple connections/providers is usually for failover not to work around poor isp service.