Feature changed by: Bruno Limmer (brunomcl) Feature #312854, revision 2 Title: make nfs-server and nfs-client setup in YaST themselves deal with the Firewall openSUSE 12.1: Unconfirmed Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Steffen Eibicht (steffen13) Partner organization: openSUSE.org Description: Hi, when setting up a NFS Server or a NFS client, you can tick "open firewall port" That is really convinient. But there are also other services involved with NFS, which also require some modifications to the firewall. As far as I understood (I do not have that much clue about all this), it is rpc.mountd and rpc.statd, which need to go through the firewall as well. So the normal user (like me) is not able to setup NFS at home, without switching off the firewall completely as it seems like that you can not force these two services to use ports, which you specify as open. Switching off the firewall completely is a workaround but it leaves a bitter taste, as it lowers the security. So it would be cool, if YaST could take care of all services related to NFS in terms of firewall settings and also the settings coming from the NFS setup Business case (Partner benefit): openSUSE.org: it would increase the security of the system if you do not need to switch off the firewall completely. And of course it would make YaST and openSUSE even better, as this then fullfills the promise, YaST makes as an convinient tool. + Discussion: + #1: Bruno Limmer (brunomcl) (2011-10-01 20:49:17) + Absolutely. Setting up a home/soho nfs share is not a trivial exercise, + even if Yast does most of the job. -- openSUSE Feature: https://features.opensuse.org/312854

Feature changed by: Steffen Eibicht (steffen13) Feature #312854, revision 5 Title: make nfs-server and nfs-client setup in YaST themselves deal with the Firewall openSUSE 12.1: Unconfirmed Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Steffen Eibicht (steffen13) Partner organization: openSUSE.org Description: Hi, when setting up a NFS Server or a NFS client, you can tick "open firewall port" That is really convinient. But there are also other services involved with NFS, which also require some modifications to the firewall. As far as I understood (I do not have that much clue about all this), it is rpc.mountd and rpc.statd, which need to go through the firewall as well. So the normal user (like me) is not able to setup NFS at home, without switching off the firewall completely as it seems like that you can not force these two services to use ports, which you specify as open. Switching off the firewall completely is a workaround but it leaves a bitter taste, as it lowers the security. So it would be cool, if YaST could take care of all services related to NFS in terms of firewall settings and also the settings coming from the NFS setup Business case (Partner benefit): openSUSE.org: it would increase the security of the system if you do not need to switch off the firewall completely. And of course it would make YaST and openSUSE even better, as this then fullfills the promise, YaST makes as an convinient tool. Discussion: #1: Bruno Limmer (brunomcl) (2011-10-01 20:49:17) Absolutely. Setting up a home/soho nfs share is not a trivial exercise, even if Yast does most of the job. #2: Ludwig Nussel (lnussel) (2011-10-04 17:05:28) All requires ports are listed in /etc/sysconfig/SuSEfirewall2. d/services/nfs-kernel-server already + #3: Steffen Eibicht (steffen13) (2011-10-18 03:33:36) (reply to #2) + ok... but why does YaST not open them, when I tick "open firewall + port"? On my system NFS only works without firewall right now. I could + not figure out how to do it with enabled firewall. + Is this behaviour maybe a bug, which should be reported? -- openSUSE Feature: https://features.opensuse.org/312854