From there, work out the destination port, and include it in
It appears that NFS server on a Suse 9.3 box is blockec from serving clients by its firewall. The NFSServer service is set up under yast2 with Open port in firewall option selected. Within the firewall setup, all interfaces are in External zone, and the Allowed services include NFS client and NFS server. No joy. Dmesg reveals that the packets are dropped. the firewall advanced option on tcp port. Now NFS is serving ok. But this is unsatisfactory, as the NFS request port can vary...
On Thursday 22 September 2005 09:29, Chiu, PCM (Peter) wrote:
It appears that NFS server on a Suse 9.3 box is blockec from serving clients by its firewall.
The NFSServer service is set up under yast2 with Open port in firewall option selected.
Within the firewall setup, all interfaces are in External zone, and the Allowed services include NFS client and NFS server.
No joy.
Dmesg reveals that the packets are dropped. From there, work out the destination port, and include it in the firewall advanced option on tcp port. Now NFS is serving ok.
But this is unsatisfactory, as the NFS request port can vary...
I needed to support NFS mounts and also had trouble getting it to work through the firewall. I did get it working after some changes to the firewall configuration. Here is a line from my /etc/sysconfig/SuSEfirewall2: FW_SERVICES_EXT_RPC="mountd nfs nfs_acl nlockmgr portmap status" I am no longer running an NFS server so I can't be 100% sure that the above is enough. It may also include things that are not required. Anyway, maybe comparing to what you have will help. Bob
participants (2)
-
Chiu, PCM (Peter) -
Robert Paulsen