You can come pretty close by using /etc/exports to control what IP addresses can access the NFS shares. This doesn't really get tied to a particular interface, per se, but it does allow you to limit which systems can get to what shares. "man exports" will explain how you do that.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Wednesday, March 09, 2005 12:03 PM To: [email protected] Subject: NFS and specific ethernet interfaces Is it possible to set up NFS so that it only exposes local NFS shares to a specific ethernet interface? I am goign to take a shot at having a side scanning engine running to do file system antivirus scanning via NFS mount. After enough people perked up and gave me advice I could shake in front of my management, they have become more amenable to having a wintel box. That said, I am not comfortable exposing the entire file system via NFS unless I can control what ethernet interface the NFS access can be accomplished by. I intend to dedicate a 100 mbit osa port to VM and the linux machines, and borrow a 2 or 4 way cast off server that was heading to the junk pile (Ahem.... Depreciated asset pile) and see how it all works. It would make me feel better from a security stand point if I could dedicate the specific shares to a specific ehternet interface. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
