Re: mountd through a firewall?

[Robert Rati <Robert.Rati@motorola.com>]

>>I've tried using the -p option, but that causes mountd to try to open 
>>all 4 ports on the same port.  For the two UDP ports that not a problem 
>>(although I don't think functionally it'd work too well), but the two 
>>TCP ports obviously will have a problem.  When I run rpc.mountd -p 5000, 
>>I get this error:
>>
>>mountd: Could not bind name to socket: Address already in use
> 
> 
> Then you have a broken mountd.. because it doesn't need to listen on 
> multiple ports. You saw my rpcinfo output, even without -p it was only 
> using 2 distinct ports.
> 
> I just tested the mountd from both nfs-utils 0.3.3 and 1.0.1, both work 
> correctly with respect to -p.

rpc.mountd -version gives this info:

kmountd 1.4.7 (0.4.22)

and I don't have nfs-utils installed on the system.  I'm stuck using 
kernel 2.2.17 and I had read you had to have a 2.4 kernel to use 
nfs-utils.  Is that incorrect?  Is this possibly a limitation of the 
version of mountd on the system?

Rob



-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs