Re: Force NFS mount to a specific TCP/IP interface -- MIDRANGE-L

Subject: Re: Force NFS mount to a specific TCP/IP interface
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Tue, 10 May 2011 11:00:43 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I thought it might, but it's not working the way I thought it would. My numerically lower IP has no entry in the routing table and a higher one is defined as the preferred interface for a specific subnet. Traffic destined for the specified subnet goes out the LOWER interface, traffic outside of the subnet goes out to the HIGHER interface. Exactly opposite what I expected.

I'll post more info when I get more time.

Joe

If you add a host route to the remote server and bind it to the specific interface you want to use, will it work?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.