General discussion


two pipes one network

By scott_baldridge ·
Hello all, I need some direction on how to join two internet services for one network so that network resources can be shared.

I have comcast broadband service and bellsouth DSL service coming into our company. I want to segment the network so that I can split up clients to load balance between the two services.

Each of the services(service A and service B) have a linksys router and a 32 port switch. I have 4 servers on segment A and need clients on the B segment to touch resources on the A segment. Currently, I have one PDC on segment A. The linksys routers handel DHCP on their segments.

Can someone please explain the various options I have to accomplish this?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to two pipes one network

gonna need another piece of hardware or something like ISA 2004 [not ISA 2000] that can do NLB on the WAN links.

Cisco, Symantec have hardware that I know of that can do NLB on multiple WAN DSL links, but its pricey stuff.

Collapse -

by curlergirl In reply to two pipes one network

I think you are already on this wavelength, but just to confirm, we are talking about manually "load balancing" between the two routers by splitting your network into two subnets. Any kind of automatic load balancing would require some fairly sophisticated and expensive routers.

Without having specific IP addressing info, here's generally what you want to do. On Segment A, all workstations/servers use the Segment A Linksys router as their default gateway. On Segment B, all workstations/servers use Segment B router as their default gateway. On Segment B router, create a static route to the Segment A router, to route traffic from workstations/servers on Segment B to Segment A's subnet. On Segment A, create a static route to the Segment B router, to route that traffic to Segment B. Routers need to have a physical connection between them (a third hub or switch, or uplink port from one router's hub to the other).

Another idea - if you don't really need to segment the network (i.e., if it's small enough to use one IP subnet throughout the whole network), you could put your routers in the same subnet and limit their DHCP scopes so that they would handle only a certain number of workstations. What I'm not sure about in this scenario (because I've never tried it), is whether you would be prone to having DHCP communication errors on the workstations when they can't get an IP addy from the same router they got from last time. However, this probably wouldn't happen too frequently, as once the workstations got their IPs they would be likely to simply renew the same one over and over from the same router. If you really have a small network, you could even just turn off DHCP and set all workstations and servers statically. As an example, say you have 100 workstations and 3 servers:

(Continued in Comment below)

Collapse -

by curlergirl In reply to

Router A: DHCP scope -, default gateway assigned of, static LAN IP addy of

Router B: DHCP scope -, default gateway assigned of, static LAN IP addy of

All WS get DHCP addy from Router A or B in same subnet; servers have static IPs between and Everything is on the same subnet, no special routing setup needed between the routers. The number of workstations using each router is controlled simply by the number of IP addys that router has available to be assigned to workstations.

Hope this helps!

Collapse -

by zaferus In reply to two pipes one network

If your company can afford it I recommend using a firewall that can load balance at a hardware level like a Sonicwall or a Fortinet device. This will give you solid protection and definitely is keeping it simple.

Collapse -

by K12Linux In reply to two pipes one network

If you can afford a reasonable speed PC (800Mhz+ probably) with 4 NICs in it you could try using Linux. The scenario is similar to the one here ( )

You would connect one NIC each to:
Switch #1
Switch #2
Internet Connection #1
Internet Connection #2

You would set the default gateway for each subnet to be the Linux box NIC attached to that switch. Of course since you're puttin the Linux box between your Linksys and the other subnet, you probably would have to have the Linux system serve DHCP.

The link above should give you a decent start on setting up the load balancing. I suspect you could also configure it so some hosts default to specific Internet connetions if needed. Or, if it doesn't matter just let everybody be load balanced. The ability to fail over to the working connection would be an added bonus.

Warning: Do not attempt this unless you know or are interested in learning about Linux networking. I doubt you'll find a config that is an exact match to what you are asking for since most will have two+ connections to the Internet and only one to the local network.

Collapse -

by Meganetcomputers In reply to two pipes one network

Here is a quick answer for you, you can check out the following web site at:

It has several inexpensive items that you can use to perform that functions that you are looking for.

Collapse -

by wlbowers In reply to two pipes one network

Load share is to provide two or more pipes to the internet and have a router or server provide a monitored path for clients that will select the path of less resistance. To be crude.

What you need to do is get a Cisco 2600 router and load share software.

You can do all of the routing and load share in the router.

Call cisco and tell them what you are doing. They will provide a complete listing of hardware and software.

Then go to ebay.

Good Luck Lee

Collapse -

by wlbowers In reply to two pipes one network

Cisco Router 1750 or 2600 series with load share.

Cisco will help you in the config.

To obtain basic information and ask questions about Cisco products and solutions, customers in North America can call 1-800-553-NETS, option 2, between 8:00 a.m. and 8:00 p.m. Eastern Time for assistance


Collapse -

dual gateways

by marc In reply to two pipes one network

If you can manage static IPs on your nodes, it is easiest to simply assign the gateway to either of your internet connections based on the requirement for the given PC. The only cost is your time to change the gateway IP and/or assign a static IP and DNS IP's to each PC. After that its done. A word of caution, if you do intend to grow, or want to continue to use dynamic assignment with DHCP, keep your static IP block tight for example, reserve for servers, use 69.31-69.100 for dynamic assignment, then statically assign 69.101-69.254 as needed. You can of course change this as needed.

Related Discussions

Related Forums