Matt, >From your diagram I take it that eth1 is in a different subnet than eth0 and that eth1 is in the same subnet as the NFS server. That being the case all of the NFS traffic should pass thru eth1 automagically. If you run route -n you should see which interface is associated with which subnet. Bob... On Tue, 2005-09-27 at 10:30 -0400, Matt Roth wrote: > Thank you for the response. > > I should have been more specific in my original post. The multiple NICs are on the NFS client. > > One NIC on the NFS client will be receiving HEAVY VoIP traffic and I want any NFS traffic to be offloaded to a separate NIC on the client, as shown: > ________ ________ > _| |_ | | > |e| |e| | | > VoIP |t| NFS |t| NFS | NFS | > --------|h| Client |h|-------| Server | > |0| |1| | | > -|________|- |________| > > I'm looking for a way to tell the mount command on the NFS client which interface to use. It defaults to the first active interface. I can easily swap interfaces and IPs around in the box to meet my goal, but I was looking for a more flexible solution. > > I've read the pertinent man pages and the NFS section in my network administration guide but they make no mention of this. We are currently using NFS version 3. > > Thank you, > > Matthew Roth > InterMedia Marketing Solutions > Software Engineer and Systems Developer > > >> I have a NIC that I would like to dedicate to an NFS mount. After much > >> reading, I can't find any mount options that let me specify the > >> interface. Mount seems to only want to use the first active NIC on the > >> system. > >> > >> If anyone knows how to do this, I'd greatly appreciate your help. > >> > >> Thank you, > >> > >> Matthew Roth > >> InterMedia Marketing Solutions > >> Software Engineer and Systems Developer > > > > From what I can tell is you want an nfs client to attach to a certain > > nfs server interfaces. If you have the appropriate dns/host record's you > > should be able to make this happen. > > > > server01.domain.com 1.1.1.1/24 > > server01-eth1.domaincom 1.1.2.1/24 > > > > client.domain.com 1.1.1.2/24 > > client-eth1.domain.com 1.1.1.2/24 > > > > On client.domain.com > > mount server01-eth1.domain.com/exports /imports > > > > Common mistake most people tend to do is over look impact of the routing > > involved. If the client does not share a broadcast domain with the > > server, you are just going to create a heap of ____. > > > > Provide some details about your network topology with client and server > > shown for a better response. > > > > Regards, > > Ted >
