[Webinar] Learn how to a build a cloud-first strategyRegister Now


2 NICs, 2 subnets, 2 paths: can I do this?

Posted on 2004-08-09
Medium Priority
Last Modified: 2010-04-11
I have two machines, each with 2 NICs, connected to the same two subnets (192.168.1. & 192.168.2.). I was thinking of setting up my host tables like this:

On machineA: machineA machineB   # machineA looks for machineB on subnet 1

On machineB: machineA machineB   # machineB looks for machineA on subnet 2

to spread the traffic between these machines over the two subnets.  Am I setting myself up for trouble doing this?  Will it work?

I doubt it matters, but I'm running Linux (FC1).
Question by:jwolter
LVL 27

Expert Comment

ID: 11756619
I don't think this will work - you want traffic to travel in a circle?!?!?  

You might be able to get funky with host files, but if A initiates a conversation to B over subnet1, B will learn A's physical address and rember it (ARP cache) and use it to repy to A over subnet1, not subnet 2.

Are these machines only going to talk to each other?  So you won't have any default gateway?  Or would you put it on one subnet on one and vice versa?

I assume you're doing this as a learning experiment - if you're trying to load balance your connections and improve throughput, it won't work.

Expert Comment

ID: 11756811
You maybe able to configure some sort of FastEtherChannel link, whereby they will share a virtual MAC and then load balance traffic, never seen it done back to back and it is not possible with two different subnets!

Assisted Solution

Kooroo earned 100 total points
ID: 11756815
Do you mean:

On machineA: machineA <----I changed this line machineB   # machineA looks for machineB on subnet 1

On machineB: machineA machineB   # machineB looks for machineA on subnet 2

I'm not sure what you're trying to accomplish here, but it looks to me like you want to reduce the load on the switches?

It looks to me like you're trying for:
Machine A makes requests to Machine B via 192.168.1 subnet
Machine B makes requests to Machine A via the 192.168.2 subnet

Of course, this is done after a name resolution, so lower level apps which don't use hostnames would use the routing table instead.

You might have to tweak your routing tables, but it should work. The problem is, there's really no point to it beyond you having an overloaded switch. And, let's face it, if 2 workstations are generating too much traffic for your swtich, it's time to buy a new switch.
LVL 11

Accepted Solution

PennGwyn earned 100 total points
ID: 11768982
> It looks to me like you're trying for:
> Machine A makes requests to Machine B via 192.168.1 subnet
> Machine B makes requests to Machine A via the 192.168.2 subnet

That's it exactly.  And responses will go back over the same leg as the original request.  In effect, he's got a full channel for connections initiated by A, and one for connections initiated by B.

It's crude, but it will work just fine.  Each NIC will have its own MAC address, so neither machine will "know" that both the partners it's talking to are the same machine.

Author Comment

ID: 11813172
Since people were wondering what I'm trying to do here, I've actually got a whole cluster of machines, and I happen to have two switches and two NIC's on each machine.  So I thought it might be a cheap way to spread some of the load out.  Thanks for the comments everyone.


Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
This program is used to assist in finding and resolving common problems with wireless connections.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question