This may be similar to some of the dead threads here. Because of limited bandwidth available by my only "HI SPEED" provider (Frontier 3mb max) I elected to go with a 2nd DSL line from them to maybe speed things up a bit. Now I have 2 x 3 mb DSL lines. I have VOIP and security cameras on one of them that are monitored off site and partially because of that, it slows that DSL connection down. Now I have some computers that are used for "normal" applications on the 2nd line. I would like to be able to access the other DSL network from the recently installed 2nd one for a number of reasons by a 2nd direct connection that would eliminate swapping cables. I have a "Dynamic DNS" service for the other setup but connecting that way uses bandwidth from both routers. As a side note, I have a NAS that has two ethernet connections. Is it possible to connect it to both routers? (based on the "quality" of some of the answers to others I have seen here, I am reluctant to contribute financially until I see a useful answer. Sorry.

Dani AI

Generated

Short summary and practical options for based on the thread: is right that a routing-layer solution is the cleanest fix, and ’s client-side approach (Connectify) is a workable stopgap for a single PC. Below are concrete, low-risk choices and key pitfalls to avoid so the two DSL lines behave predictably without constant cable swapping.

The cleanest, most reliable approach is a true multi‑WAN gateway (a small firewall/router that supports two WANs and policy-based routing). Put both DSL modems into WAN1/WAN2 and keep one LAN. Benefits: internal devices (including the NAS) stay on the LAN and are reachable locally, you can pin VOIP/cameras to the DSL that needs static forwards, and you get failover/load policies without asymmetric routing. Many open-source firewalls (pfSense/OPNsense) and commercial multi‑WAN routers support this.

If replacing hardware is not possible, two practical alternatives: 1) Add static routes between the two existing routers (they must use different LAN subnets and allow custom static routes/firewall rules), or 2) build a site‑to‑site VPN between the routers so traffic between networks does not traverse public DNS/Internet unnecessarily. Note consumer routers vary: some block inter‑LAN routes or lack VPN/static route controls.

NAS dual‑NIC notes and a short troubleshooting checklist: do NOT attempt LACP across two independent routers (bonding requires a single coordinating device or MLAG-capable switches). Either connect the NAS to the single LAN behind a multi‑WAN gateway, or give each NIC its own IP on each subnet so services on each network use the appropriate address. Avoid two default gateways on one host; that causes asymmetric drops. On Linux/BSD you can force source-based routing for a host IP—example pattern:

echo "200 wan1" >> /etc/iproute2/rt_tables
ip route add default via <WAN1_GATEWAY_IP> dev <wan_iface> table wan1
ip rule add from <HOST_IP> lookup wan1

Test after each change (ping, traceroute, check NAT/port‑forwarding) and keep one DSL dedicated to the critical VOIP/camera traffic to avoid interruptions.

Recommended Answers

All 5 Replies

You need a router sitting between the 2 DSL drops and your internal network.

Inside you run 2 subnets, 192.168.1.0/24 and 192.168.2.0/24. Rrouter interface is 192.168.1.1 and 192.168.2.1 which will serve as the gw for each subnet. Get a router that can do policy based routing and you can send all traffic that originates from 1.0 to DSL drop 1 and all traffic that originates from 2.0 to DSL drop 2.

Linksys had an RVO42 model router years ago that supported dual Internet... probably been replaced with a newer model by now. The trick here is finding a router that will route based on source IP.

You can use loadshearing feature available in router as discrided by CimmerianX but on computer you need a sofware Connectify Dispatch to add up to internet connections. This SW is paid so you need to get licence to do.

Normaly with any DSL connection you need to reside or stay with the range of your provider to get high bandwidth.any way this is one of the drawbacks of DSl.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.