Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: NFS over the WAN
Keywords: NFS cisco WAN
Message-ID: <1990Nov21.080035.23492@Think.COM>
Date: 21 Nov 90 08:00:35 GMT
References: <1057@inews.intel.com>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 24

In article <1057@inews.intel.com> echan@cad017.cadev6.intel.com (Eldon Chan ~ ) writes:
>Would someone out there tell me what is the standard way to set up the
>access-lists
>if I just want to pass NFS, FTP, and mail traffic between to Cisco
>routers via a serial
>link.
>
>FTP and mail part is quite easy. Since NFS traffic doesn't use any fix
>UDP ports (except 111),  how can I single out the NFS traffic ?
>The approach I am using is to allow all UDP traffic and disable the UDP
>ports that I don't like.  Is it the right approach ?

Many NFS implementations, Sun in particular, actually do use fixed port
numbers rather than letting the port mapper choose the port numbers.  They
probably use the same ports as Sun's NFS uses (I've heard that until
recently Sun's NFS client didn't actually use the port mapper to find
remote NFS servers, but I haven't verified this).  You can determine the
ports that a host uses with /usr/etc/rpcinfo -p <hostname>.  Sun uses UDP
ports 2049 and 704 for NFS and MOUNT, respectively.
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar