System with 2 NICS

Mark Musone mmusone at shatterit.com
Fri Jun 4 10:33:31 EDT 2004


Just use a host based route/routes.
Heck you can also just subnet your routes accordingly just on that
machine..it's ugly but should work


-----Original Message-----
From: owner-nflug at nflug.org [mailto:owner-nflug at nflug.org] On Behalf Of
Robert Meyer
Sent: Friday, June 04, 2004 8:15 AM
To: nflug at nflug.org
Subject: Re: System with 2 NICS

Not much you can do about this.  The system will only use one route to
any
network.  Most folks that want to set up two NICs also have two separate
networks to work with.  Typically in a server environment, there would
be one
network that is private for the servers to talk to each other and one
for the
world to talk to the servers.  There is little or nothing to be gained
by
having two NICs on the same network.  If you have 100Mb to work with,
using
more than one NIC can actually hurt you because both NICs can be trying
to
transmit at the same time and the internal queueing that the machine
would
normally provide is defeated.

Cheers!

Bob
--- Robert Dege <rdege at cse.Buffalo.EDU> wrote:
> 
> I recently added a 2NIC to a server I have at work.  The server
beforms 2
> functions, it acts as a NFS File Server, and it runs Amanda (Network
> Backup software)
> 
> The way that I want the server to work is that
> 
> NIC #1 - is dedicated to NFS traffic
> NIC #2 - is dedicated to Amanda network backups
> 
> Each NIC has their own IP, and own hostname.  This way, it's easy to
point
> autofs to one host, and amanda clients tothe other host.  Both IPs are
> also in the same subnet, so I'm working within a single subnet.
> 
> here is my problem... according to netstat -rn, all outgoing
> network traffic is using NIC #2, whether the data is incoming from NIC
#1
> or NIC #2.  Here's is my netstat -rn:
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window
irtt
> Iface
> 167.225.72.0    0.0.0.0         255.255.255.0   U         0 0        0
eth1
> 167.225.72.0    0.0.0.0         255.255.255.0   U         0 0        0
eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0        0
eth1
> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0        0
lo
> 0.0.0.0         167.225.72.254  0.0.0.0         UG        0 0        0
eth1
> 
> 
> The first 2 entries are NIC #1 & NIC #2.  The 3rd entry is some Redhat
> Zeroconf crap.  Does anyone know what I have to do to get NIC #1
traffic
> to stay on NIC #1?
> 
> Any insight is appreciated.
> 
> Dege
> 
> As seen on bash.org:
> The problem with America is stupidity. I'm not saying there
> should be a capital punishment for stupidity, but why don't
> we just take the safety labels off of everything and let
> the problem solve itself?



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 




More information about the nflug mailing list