Hi, All my nfs/cifs mounts and automounts work except if I try to access a mount point through /net/<SERVER_IP>. Ex : From the client side : cd /net/<server>/home/... if /home is exported by <server>. On the client, the command : showmount -e <SERVER_IP> hangs without issuing any error message. This command is used in the file /etc/autofs/auto.net The autofs package is installed on both sides but in this case, it is the client side which is important. If I disable the server firewall, it works. If I enable it AND open the port 20048 (in both udp and tcp, not sure this is required), it works. I think this port should be automatically open when the nfs packages are installed or at least the a pop-up explains that access to the server from a client using /net/server needs this port to be open. Regards. Xuo.
Assigning initially to Guillaume as the nfs-utils maintainer.
Assignee: bugsquad => guillomovitchSource RPM: (none) => nfs-utils-2.3.4-3.mga7.src.rpm
Technically, it is quite difficult to interact with a firewall without knowledge of local filtering policy. Which source address should be allowed, for instance ? And if you're paranoid enough to install a local firewall, usually, it is to control your network traffic finely, so I don't see the point of automatically opening anything on install. But more generally, NFS is a network service, as well as many others we ship in the distribution. Do we really need to explain anyone installing such a service than he also need to configure its firewall properly ? We may as well explain he needs to configure the service, read related documentation, or any other implicit expectation. And for every similar service in the distribution, such as samba, apache, etc...
Hi, I didn't think I was paranoid if I wanted to enable a local firewall. Maybe I am. In the MCC, when I want to enable NFS, the nfs ports are automatically open without the need of reading any doc. This was my request. Regards. Xuo.
CC: (none) => xuoyResolution: (none) => FIXEDStatus: NEW => RESOLVED